promotions_code_delete

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

The destructiveHint annotation already signals a destructive operation. The description adds minimal context: it specifies 'unused' but does not explain behavior if the code is already used, effects on related data, or whether deletion is irreversible. It relies heavily on 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?

The description is a single sentence and a link, which is concise and front-loaded. However, the link may not be actionable by the agent. It is efficient but could be slightly more informative without losing conciseness.

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 operation with two required parameters and no output schema, the description is incomplete. It lacks information on return values, error conditions (e.g., code already used), and any prerequisites like partnerId that might be needed. The link partially compensates but is not fully integrated.

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 50%; only promotionCode has a description. The description does not add meaning for promotionId and does not elaborate on the format or constraints of either parameter, leaving the agent to infer from the schema.

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 the verb 'Delete' and specifies the resource as 'unused single-use code', clearly indicating the action and scope. It distinguishes from sibling tools like promotions_code_get and promotions_codes_list by narrowing to deletion of unused single-use codes.

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 provides no guidance on when to use this tool versus alternatives, such as when a code is already used or for batch deletion. No exclusions or prerequisites are mentioned.

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