google_ads_callouts_list

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

With no annotations provided, the description carries the full disclosure burden. It states the tool is 'Read-only,' notes that it only scans campaign_asset rows (no account-level merge), and reveals a hardcoded limit of 20 callouts per campaign. These are meaningful behavioral traits beyond basic read/write classification.

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 three succinct sentences with no filler. It front-loads the core action and return format, then adds differentiation and usage guidance efficiently. Every sentence earns its place.

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 no output schema, the description specifies the exact return format ([{id, resource_name, callout_text}]). It also includes operational context (read-only, audit before create/remove, hardcoded limit) and sibling differentiation. This is complete for a straightforward list tool.

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 description coverage is 100%: campaign_id is described as a numeric string without dashes and obtainable via google_ads_campaigns_list, and customer_id includes fallback behavior. The description adds no extra parameter meaning beyond the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb+resource: 'List callout extension assets linked to a Google Ads campaign.' It also distinguishes itself from the sibling tool google_ads_sitelinks_list by clarifying that it only scans campaign_asset rows without account-level merge, making its scope unambiguous.

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 explicitly states when to use this tool: 'Use this to audit coverage before calling google_ads_callouts_create or google_ads_callouts_remove.' It also contrasts with google_ads_sitelinks_list, giving clear guidance on when this tool is appropriate versus an alternative.

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