yelp_place: GET /

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

With no annotations provided, the description bears the full burden. It lists returned fields, which adds beyond the schema, but it does not disclose whether the operation is read-only, any required permissions, or potential side effects. The agent must infer safety from 'fetches'.

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 long and concise, front-loading the purpose and then listing return fields and use cases. It is clear and efficient, though a slight structuring issue (e.g., bullet points) could improve readability.

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?

Given the absence of an output schema, the description should hint at the return structure. It lists fields but does not explain format (e.g., single JSON object, pagination). Edge cases like missing place ID are not addressed. Sibling differentiation from Google Maps place tool is absent.

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?

Schema coverage is 100% with both parameters described in the schema. The description mentions 'domain targeting' but adds no additional semantic detail beyond what the schema already provides. The baseline of 3 is appropriate.

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 it 'Fetches a single Yelp business by Yelp ID or alias', which is a specific verb+resource. It lists the returned fields and provides three distinct use cases, distinguishing it from the sibling 'hasdata_yelp_search_getSearchResults' which returns multiple results.

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 explicitly lists use cases (enrich leads, monitor competitor, validate hours/amenities), giving clear context for when to use this tool. However, it does not mention when not to use it or explicitly compare it to alternatives like the Yelp search tool.

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