google_ads_conversions_remove

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

Discloses archival behavior: historical data remains but stops counting toward 'Conversions', return format, and destructive vs. reversible nature. No annotations exist, so description fully carries the burden.

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, front-loaded with purpose, uses bold for emphasis. 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 return value, effect, re-enabling, and alternative. Given no output schema, the description is complete for a simple deletion 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?

Both parameters are already described in the schema (100% coverage). Description adds context: optional customer_id falls back to credentials, conversion_action_id obtainable via list tool. Slightly above baseline.

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 clearly states the tool archives (status=REMOVED) a Google Ads conversion action, using a specific verb and resource. It differentiates from siblings by mentioning 'HIDDEN' status via google_ads_conversions_update.

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?

Explicitly tells when to use (to archive) and when not to (for soft-hide, use update with HIDDEN). Provides re-enabling guidance and alternative tool name.

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