yelp_get_business

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get details' which implies read-only, but does not disclose error behavior (e.g., if ID not found), rate limits, authentication requirements (api_key is optional but not explained), or response format.

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 extremely short (one sentence), which is efficient but sacrifices necessary detail. It is front-loaded with the core purpose, but the lack of additional information makes it minimally viable rather than well-structured.

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 tool has no output schema and low parameter documentation, the description should provide more context about what 'details' are returned (e.g., name, address, rating, hours). It fails to do so, leaving the agent without expectations for the return value.

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 description coverage is 0%, so the description must compensate. However, it only mentions business_id indirectly and does not explain the api_key parameter at all. The description adds no meaning beyond the parameter names, leaving users unclear about the api_key's purpose or when it is needed.

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 'Get details for a Yelp business by ID', using a specific verb and resource. It effectively distinguishes from sibling tools like yelp_search_businesses (search) and yelp_get_reviews (reviews), making it clear what this tool uniquely does.

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?

No guidance is given on when to use this tool versus alternatives. For example, it does not mention that the business ID should be obtained from yelp_search_businesses first, or any prerequisites. The description lacks context for appropriate usage.

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