yelp_geocode

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the burden. It discloses the backend (Yelp Android app), credential-free access, and non-business scope, which add transparency beyond the schema. However, it does not describe failure behavior (e.g., invalid address handling) or return format details beyond listing fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the core purpose. Every sentence adds value: backend distinction, credential-free fact, and non-business scope. No redundant words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description lists output fields (coordinates, city, state, zip, county), which is helpful. However, it does not explain the exact response shape, possible absence of results, or error handling. Given the tool's simplicity and one parameter, it is adequate but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers the single parameter (address) at 100% with a description. The tool description repeats the term 'free-form address' but adds no new parameter-specific semantics. Baseline 3 is appropriate since schema fully documents the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Geocode a free-form address') and the output (structured location data: coordinates, city, state, zip, county). It also distinguishes from siblings by noting 'via Yelp's real Android app backend' and 'Not business-scoped,' which sets it apart from yelp_business and generic geocoding tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives like geocoding_search or yelp_business. It notes 'Not business-scoped' as a negative scope, but gives no exclusions or alternative tool names. Usage context is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.