google_ads_conversions_remove

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

The description is fully transparent about the tool's destructive nature: 'Destructive — historical data remains but the action stops counting toward Conversions.' It also states the return value ('Returns {resource_name}') and the effect on data. Since no annotations are provided, the description carries the full burden and meets it well.

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 sentences long, front-loading the action and return value. Every sentence adds essential information without redundancy, making it highly concise and well-structured.

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?

For a simple removal tool with two parameters and no output schema, the description is complete. It covers behavior, consequences, return value, and alternatives, leaving no gaps given the tool's complexity.

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. The description adds value by noting that conversion_action_id can be obtained via google_ads_conversions_list, providing contextual guidance beyond the schema. This justifies a score of 4.

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 action: 'Archive (status=REMOVED) a Google Ads conversion action.' It specifies the verb and resource, and distinguishes the tool from siblings by mentioning google_ads_conversions_update with 'ENABLED' and 'HIDDEN' statuses, making it clear when to use this tool versus alternatives.

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 provides explicit guidance on when to use this tool (for archiving) and when not to ('For soft-hide... use google_ads_conversions_update'). It also mentions the alternative tool and the re-enabling path, offering clear context for decision-making.

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