deactivate_code_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. The description only states the action and that it does not delete, but omits behavioral details such as side effects (e.g., impact on existing carts or orders), reversibility (implied 'pause'), or state changes. Minimal transparency for a mutation tool.

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 a single, 10-word sentence that is front-loaded and efficient. Every word contributes to the understanding. No wasted content.

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?

The tool is simple with one parameter and no output schema. The description is adequate for the core action but lacks context on the implications of deactivating (e.g., whether it can be reactivated, if it affects active discounts). Given sibling tools like activate_code_discount, more completion could be helpful.

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% with one parameter ('id') fully described as 'GID of the discount node.' The tool description does not add additional meaning beyond the schema—baseline 3 is appropriate.

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 uses a specific verb ('deactivate/pause') and resource ('code discount'), and explicitly distinguishes from deletion ('without deleting it'). This clarifies the tool's purpose and differentiation from sibling tools like delete_code_discount.

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 implies when to use (when you want to temporarily disable a discount) and not to use (when you want to permanently remove it), but lacks explicit guidance on when to deactivate vs. activate or delete. No alternatives or context provided.

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