Yellowpages Search

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 references a 'documented endpoint' without mentioning sync/async options, return format, rate limits, or authentication needs, providing zero behavioral insight.

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 a single sentence with clear structure, but the phrase 'with the documented /yellowpages-search endpoint' is redundant given the tool name and adds little value. It is concise but not maximally efficient in communicating useful information.

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's complexity (9 parameters, execution modes, output schema), a one-sentence description is insufficient. There is no guidance on query construction, region/location handling, or enrichment usage, making correct tool invocation difficult without external documentation.

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 provides descriptions for all nine parameters, so the baseline is 3. The tool description adds no parameter-level meaning beyond the schema, and the 'documented endpoint' phrase does not clarify any parameter semantics.

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 ('Search') and resource ('Yellowpages'), making the core purpose explicit. However, it does not differentiate this from sibling search tools like google_search or businesses_search, nor does it specify the type of data returned.

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?

There is no guidance on when to use this tool versus alternatives. The description lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer applicability solely from the tool name.

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