yelp_search_businesses

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

No annotations are provided, so the description must bear the full burden of disclosing behavioral traits. It only states the action (search) without describing what the tool returns, whether it has side effects, or any constraints (e.g., rate limits, pagination). For a search tool, the lack of output format details is a significant gap.

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 concise at one sentence with no wasted words. While it could benefit from additional context, it does not contain any filler or redundancy, earning a high score for efficiency.

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 and annotations, the description is insufficiently complete. It does not explain the result format, any default behavior (e.g., ordering, limits), or how it complements sibling tools like yelp_get_reviews. An agent would have to infer many details from the tool name alone.

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 input schema already has 100% parameter description coverage, providing clear meaning for all three parameters (query, category, location). The description adds no extra information about the parameters, so it meets the baseline expectation without exceeding it.

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 states the tool searches for any type of business on Yelp and explicitly clarifies it is not limited to restaurants, which distinguishes it from a common assumption. However, it does not specify that the search uses query and location parameters, leaving some ambiguity about how the search is performed.

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 provided on when to use this tool versus its siblings (yelp_get_deals, yelp_get_hours, etc.). The description does not mention prerequisites, limitations, or alternative tools, leaving the agent to infer the appropriate context from the tool name and siblings alone.

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