delete_discount

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only that a discount code is deleted, without mentioning whether the deletion is permanent, whether it cascades, whether it requires special permissions, or what happens to associated data. For a destructive operation, this is insufficient.

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 extremely concise, front-loaded, and contains no filler. It is appropriately sized for a simple one-parameter delete tool, though the brevity contributes to missing contextual details.

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 tool with one required parameter and an output schema, the description plus schema provide a minimal callable definition. However, the lack of destructive-behavior context and parameter-source guidance leaves clear gaps that matter for correct and safe invocation.

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%, and the description does not explain the discount_id parameter beyond implying it identifies a discount code. It does not indicate how to obtain a valid ID, whether the ID must be globally unique, or any format expectations. The description fails to compensate for the missing schema-level parameter documentation.

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 'Delete a discount code' uses a specific verb and resource, clearly identifying what the tool does. It is also distinguishable from sibling delete tools like delete_event or delete_webhook by naming the discount resource. It lacks extra scoping detail, but the core purpose is unambiguous.

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?

No guidance is provided about when to use this tool versus alternatives such as update_discount or get_discount. The description only implies usage through the verb 'Delete'. There is no mention of prerequisites, exclusions, or when a different discount-related tool should be chosen.

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