search_ads

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns an 'advertisement_search_id' for subsequent lookup, which is helpful. However, it does not mention pagination behavior, rate limits, or authentication requirements. The schema indicates pagination parameters, but the description remains silent on how results are delivered.

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 with two front-loaded sentences. The first sentence covers the core action and filters, and the second sentence provides a key output detail and links to a related tool. Every phrase earns its place without 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?

Given the tool has 13 parameters, no required fields, and no output schema, the description should provide more context about the response structure and pagination. It mentions the return of 'advertisement_search_id' but does not clarify if the response is an array of results or includes metadata. This is a notable gap for completeness.

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 100% with each parameter having a description. The description adds minimal extra meaning by summarizing the main filter types (keyword, headline, target location, date) already covered in the schema. Baseline score of 3 is appropriate as the description does not significantly enhance parameter understanding beyond the 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 uses a specific verb 'Search' and identifies the resource as 'company advertisements and ad campaigns'. It lists key filters (keyword, headline, target location, date) and distinctively returns an 'advertisement_search_id' for use with 'lookup_advertisement'. This clearly differentiates from sibling search tools like 'search_companies' or 'search_jobs'.

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 when searching for company ads, but it does not explicitly state when to use this tool versus alternatives. It provides a hint about a workflow by mentioning the return ID can be used with 'lookup_advertisement', but lacks explicit guidance on prerequisites or exclusion conditions.

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