search_advertisers

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

No annotations are provided, and the description only mentions the return fields (id, name, region, ad_count). It lacks details on behavioral traits such as pagination, result limits, ordering, or any side effects.

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 well-structured with Args/Returns sections and is clear, though the 'Args:' line is slightly redundant since there is only one parameter. It is efficient overall.

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 an output schema (context signal: true), the description provides the return fields sufficiently. For a simple one-parameter search tool, it is nearly complete, but lacks behavioral details like pagination.

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 coverage is 0% for the only parameter 'query', but the description adds concrete examples ('Nike', 'Coinbase', 'crypto exchange'), giving clear semantic meaning beyond the raw schema.

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 searches for advertisers by keyword or company name, with a specific verb ('Search') and resource ('advertisers'). It distinguishes from siblings like 'search_advertiser_by_domain' which is a different search variant.

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?

The description implies usage by providing example queries (e.g., 'Nike'), but does not explicitly state when to use this vs alternatives, nor does it mention when not to use it.

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