Delete a product group

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real value beyond them: the downstream consequence that ads promoting the group stop, and the irreversible nature of the operation. It also surfaces the confirm-token gate, which appears nowhere in the annotations.

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?

Two sentences, no filler. The operation and its destructive effect come first, with the confirmation requirement front-loaded in the second sentence.

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 destructive three-parameter mutation with no output schema, the description covers the essentials an agent needs: consequence, irreversibility, and the confirmation protocol. Only the ad_account_id parameter (likely optional/derived) is left unaddressed.

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 0%, so the description must carry the burden, and it only explains one of three parameters — the exact value required for confirm ('DELETE'), which is genuinely useful given the empty-string default. ad_account_id remains unexplained, and product_group_id is only implied by the tool name.

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?

States a specific verb and resource: 'Delete a catalog product group.' The catalog/product-group scope cleanly separates it from the sibling set (list/create/update_product_group, delete_audience) without ambiguity about what operation is performed.

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?

Gives a clear precondition: the call requires confirm='DELETE' and only after the user agrees. It does not name an alternative path (e.g., pause via update_product_group if the user only wants ads to stop), which is the one missing routing hint.

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