Delete discount

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that: it does not say deletion is permanent, whether redemptions or attached subscriptions are affected, or what the 'confirm' flag changes. Minimal added value over structured fields.

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?

A single front-loaded sentence with no filler. It is not padded or repetitive, though its brevity borders on under-specification for a destructive operation.

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, non-idempotent delete the annotations carry the safety profile and the schema documents all three parameters, so the core need is met. Still missing is any statement of permanence, of the confirm-gating requirement, or of side effects on related resources such as discount redemptions.

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 100%, with the schema itself explaining that 'id' is an opaque native resource ID, that 'account' is a private profile label, and that 'confirm' should be set true only for exactly this action. The description only restates the ID requirement, so it neither compensates for nor extends the schema; baseline 3 applies.

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 ('Delete') and resource ('a discount'), with the identifying parameter ('given ID'). It is clearly distinguishable from sibling delete_webhook and from get_discount/list_discounts by the resource alone, though it does not explicitly contrast itself with them.

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?

There is no guidance on when to use this tool versus alternatives (e.g., update_discount to deactivate instead of delete), no prerequisites, and no warning about irreversibility. The 'confirm' parameter implies a user-confirmation workflow, but the description never says so.

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