google_ads_callouts_list

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

Declares read-only and explains it only scans campaign_asset rows (no account-level merge). No annotations to contradict; additional behavioral details like rate limits or permissions not mentioned.

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?

Three concise sentences covering purpose, differentiation, and usage guidance. No redundant text.

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?

Provides return format, related tools, and hardcoded limit. Lacks pagination details but sufficient for a read-only list tool with no output schema.

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 has 100% coverage; description adds fallback for customer_id and suggests obtaining campaign_id via google_ads_campaigns_list, plus explains return structure.

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?

Clearly states it lists callout extension assets for a campaign, and explicitly distinguishes from google_ads_sitelinks_list.

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?

Provides explicit usage context: audit coverage before create/remove, mentions the 20 callout limit, and contrasts with sitelinks_list.

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