yelp_business_data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether operations are read-only, network-dependent, or require authentication, nor does it describe result limitations or error behavior. The operation names imply read-only retrieval, but the description offers no explicit safety or side-effect context.

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 compact, well-structured, and front-loaded with the tool's purpose. Operations are listed in a bullet list with required parameters, and the usage note is a single sentence. Every sentence earns its place with no redundancy.

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?

The tool has three distinct operations and no output schema, yet the description covers operation selection, required arguments, and the sibling alternative in a concise format. It lacks details about return value structure or any special behaviors, but it provides enough for an agent to select and invoke the tool correctly in the common case.

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's args is a generic object with additionalProperties, deferring all parameter meaning to the description. The description clearly lists required parameters per operation (query and location for business_search; business_id for details and reviews), which is essential for correct invocation. However, it does not describe optional parameters, types, or formatting, so it is not a 5.

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 covers three Yelp-specific operations: business search, business details, and business reviews. It uses distinct verbs per resource and explicitly differentiates itself from the sibling tool local_business_data.

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?

It explicitly says 'Use for Yelp specifically' and directs users to local_business_data for Google Maps businesses, providing a clear when-to-use and alternative. The operation list also clarifies how to choose among the tool's own functions.

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