yelp_autocomplete

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

The description only states the basic action, with no annotations available. It does not disclose any behavioral traits such as rate limits, authentication requirements, or what the returned data includes (e.g., list of suggestions). The api_key parameter is not mentioned, even though it is in the schema. This is insufficient for an agent to understand the tool's behavior.

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 (one short sentence), but it sacrifices essential information. While brevity is good, this is under-specification. It should include parameter details or usage context to be valuable.

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 complexity of 4 parameters (including an api_key) and no output schema or annotations, the description is grossly incomplete. It fails to clarify the role of latitude/longitude, whether api_key is required, or what the autocomplete response contains. A complete description would at least mention these aspects.

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 has 4 parameters with 0% description coverage. The description provides no explanation for any of the parameters (text, latitude, longitude, api_key). The agent has no guidance on what each parameter means or how to use them, which is a critical gap.

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 ('Autocomplete') and resource ('a Yelp business search'). It is specific enough to distinguish from sibling tools like yelp_search_businesses, which searches for businesses, while this provides autocomplete suggestions. However, it lacks any details about the scope or output format.

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 on when to use this tool versus alternatives. It does not mention when to use autocomplete vs. search, nor does it provide any context about prerequisites or typical use cases. The description simply states what it does without any usage direction.

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