create-discount-code

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

With no annotations, the description carries the burden of disclosing behavior. It does state the outcome (a discount code customers can enter at checkout) and the discount type/scope, but it omits side effects such as admin visibility, activation timing based on startsAt, duplication behavior, or what happens after creation.

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?

One tight, front-loaded sentence with no filler. Every clause adds relevant context: the action, the discount type, the scope, and how the code is used.

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 description is adequate for selecting the tool and understanding its core effect, but with no annotations and no output schema it leaves gaps: no indication of the response/return value, no prerequisites, and no warnings about duplicate or conflicting codes. For a 7-parameter mutation, this is a minimal but not fully complete description.

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%, so the schema already documents all seven parameters and defaults. The description adds no parameter-level details beyond the 'percentage or fixed amount' distinction, which is already expressed by the valueType enum.

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 opens with a specific verb-resource pair ('Create a basic discount code') and immediately defines the scope: percentage or fixed amount off the whole order, entered at checkout. This clearly differentiates from sibling tools like update-product or adjust-inventory.

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 word 'basic' implies this tool is for simple, order-level discounts, but it never explicitly states when to use it versus alternative discount-creation flows or when not to use it. No exclusions or alternative tools are mentioned, leaving usage context to be inferred.

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