google_ads_callouts_remove

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

Explicitly states that the operation is destructive ('the callout stops serving') but the Asset row is not deleted. Provides clear behavioral context beyond the schema and annotations (none provided). No contradictions.

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 sentences, front-loaded with the action, and every sentence adds essential information. No wasted words.

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?

Covers the action, return value, destructive nature, and sibling tools. Without output schema, it explains return. Could mention error handling or permissions, but overall sufficient.

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%, so baseline is 3. Description adds value by specifying sources for campaign_id (google_ads_campaigns_list) and asset_id (google_ads_callouts_list), and notes customer_id fallback. This aids correct parameter usage.

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 the action (detach/remove a callout asset), the resource (CampaignAsset link), and the return value ({resource_name}). Distinguishes from siblings by mentioning create and list operations.

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 guidance on when to use this tool (to detach a callout) and when to use alternatives (google_ads_callouts_create for re-enabling, google_ads_callouts_list for listing). Could be improved by explicitly stating when not to use it (e.g., if you want to delete the asset entirely).

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