CCA-F: Claude Certified Architect — Foundations

Question

An agent uses three tools: get_property_details(property_id), which returns data including a street address; get_price_history(property_id), which returns historical pricing; and get_neighborhood_info(address), which returns area statistics.

You observe that get_neighborhood_info always requires get_property_details to run first solely to extract the address, even when users identify the property by ID. This introduces unnecessary latency and failure coupling—if the first call fails, the neighborhood request fails as well. What tool-design change best resolves this?

Explanation

get_neighborhood_info should accept property_id and perform any necessary address resolution internally. This lets callers use the identifier they already have, eliminates an unnecessary externally orchestrated tool dependency, and prevents failure of the address-details call from blocking the neighborhood lookup.

CCA-F: Claude Certified Architect — Foundations

AstroTutor

Notes

Readiness

QuestionQ40

Community Discussion