google_ads_advertisers

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

No annotations are provided, so the description must disclose behavior. It states return fields (id, country, ad count) and downstream usage, which is helpful. However, it omits details like rate limits, pagination, or explicit read-only nature, though 'Find' implies a safe operation.

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?

Two sentences, front-loaded with the primary action, and the second sentence adds critical workflow information. No filler or 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?

Despite lacking an output schema, the description explains return fields and how to chain to google_ads_creatives. For a simple two-parameter search tool, this is adequately complete, though it doesn't cover edge cases like empty results or 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 100% with descriptions for both keyword and limit, so the schema already handles parameter meaning. The description adds context about using the returned id with google_ads_creatives, but doesn't introduce new parameter-specific details.

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 states 'Find advertisers in Google's Ads Transparency Center by name' with a specific verb and resource, and distinguishes from sibling google_ads_creatives by instructing to pass the id there.

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 clearly implies the search use case and directs the user to google_ads_creatives for creatives, providing context for when to use this tool. It lacks explicit 'do not use when' exclusions but offers sufficient guidance for the main workflow.

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