delete_promo_code

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

With no annotations, the description fully discloses irreversible deletion, authentication, concurrency limits, read-only/dry-run respect, and 404 behavior for invalid IDs.

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?

Well-structured with a clear section for purpose, guidelines, behavioral notes, args, and returns. Concise but missing minor opportunity to trim repetitive phrases.

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?

Covers action, alternatives, behavioral traits, all parameters, and return format. With an existing output schema, the Returns section sufficiently describes the response.

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?

Since schema coverage is 0%, the description provides brief but meaningful explanations for each parameter (store_id, promo_rule_id, promo_code_id), adding value beyond titles.

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 clearly states the tool deletes a promo code permanently, using specific verbs and resource. It also distinguishes from sibling tools like update_promo_code and delete_promo_rule.

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?

Explicitly provides when to use alternatives (update_promo_code to disable, delete_promo_rule to remove rule and codes), guiding the agent on proper selection.

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