Draft removing a conversion action

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

Explains the conceptual effect of removal (stops counting, drops from goal lists, preserves history, irreversible). Since annotations only show readOnlyHint=false and destructiveHint=false, this context is additive and not contradictory for a draft operation.

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?

Compact, well-structured description with a clear purpose, follow-up instruction, and constraint note. 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?

Provides the essential workflow (draft -> confirm_and_apply) and key restrictions, and an output schema is present. Minor gap is lack of explicit parameter guidance for the two input fields.

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?

Input schema has 0% parameter descriptions and the description does not explain customer_id or conversion_action_id format/value. The target is inferable from the tool name, but the description does not compensate for the missing schema detail.

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 drafts a removal of a ConversionAction and returns a preview. Distinguishes from sibling draft_create and draft_update actions.

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 instructs to call confirm_and_apply with the returned plan_id to execute, and notes SMART_CAMPAIGN_* and GOOGLE_HOSTED types will reject removal, giving the agent actionable selection and post-draft steps.

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