google_ads_transparency

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it enumerates the returned creative fields, discloses the one-page-at-a-time pagination model with the token match requirement, and notes the upstream provider (SerpAPI). It does not mention rate limits or failure modes, keeping it short of a 5.

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 lead sentence front-loads purpose, followed by a return-shape paragraph and a compact Args block. The Args block largely restates parameter names but is justified given the zero schema coverage. Slight redundancy between the pagination sentence and the page_token entry keeps it from a 5.

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?

For a four-parameter read tool with no output schema, the description covers purpose, returned fields, pagination mechanics, per-parameter meaning, and provider. An agent has everything needed to call it correctly and to continue through pages without guessing.

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?

With schema description coverage at 0%, the description fully compensates: advertiser_name gets format guidance and example domains, region gets its default plus four concrete codes, limit gets default and a max of 40, and page_token is tied explicitly to the returned next_page_token. Every parameter has meaning the bare schema lacks.

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 opening sentence names a specific verb, resource, and data source ('See what Google Ads a competitor is running via the Ads Transparency Center'), which is enough to distinguish it from a sibling like meta_ads_library without opening either schema. It also implicitly scopes the tool to Google's ad inventory rather than general search data.

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?

It states the research context (competitor ad creatives) and gives a concrete usage rule for the key input: 'Use domain, not just brand name.' Pagination guidance is explicit about passing next_page_token back with the same advertiser_name and region. It stops short of naming when to prefer a different tool or noting exclusions.

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