create_coupon

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

Annotations provide no safety hints (readOnlyHint, idempotentHint, destructiveHint all false), so the description carries the full burden. It discloses how the value parameter behaves per type, but does not reveal side effects, idempotency, behavior on duplicate codes, permissions, or return values. This is insufficient for a create operation.

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, front-loaded sentence that efficiently communicates the core purpose and the critical value parameter behavior. It is concise with no wasted words.

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?

With 6 parameters, no output schema, and unhelpful annotations, the description should cover more ground. It omits return value, error conditions, uniqueness constraints, and behavior of optional parameters, making it insufficient for fully correct 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 only 33%, with only 'code' and 'expiresAt' having schema descriptions. The description adds crucial semantics for the 'value' parameter (range and units for different types), which is valuable. However, it does not explain other undocumented parameters like maxUses or min_order_cents, leaving gaps.

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 'Create a coupon', a specific verb+resource that clearly states the tool's action. It distinguishes itself from sibling tools like list_coupons and delete_coupon by the verb 'create', leaving no ambiguity about its purpose.

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 (e.g., list_coupons, delete_coupon) or any prerequisites. It only states the creation action and value constraints, leaving usage context entirely implied.

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