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

The only annotation is destructiveHint=true, so the description must add the rest. It says nothing about uniqueness of the code text, what happens on a duplicate name, rate limits, or permissions required, and only restates that this is a POST to a fixed path.

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?

Two compact sentences, front-loaded with the action and scope, with the API endpoint as a trailing reference. Nothing is wasted.

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 6-parameter mutation with no output schema and no annotations beyond a destructive hint, the description covers the 'what' adequately but omits what the call returns (the created offer code/id that later get/update/disable calls need) and any pitfalls. Adequate but with clear gaps.

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% — every parameter including the amount_off/offer_type interaction, universal flag, and max_purchase_count is documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb (Create) and resource (offer code) and helpfully glosses the jargon as 'discount code' on 'a product', plus the backing REST endpoint. It is clearly distinguishable from get_/list_/update_offer_code siblings by the verb, though it never explicitly contrasts itself with them.

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?

There is no when-to-use guidance: nothing about preconditions (product must exist), how it relates to gumroad_update_offer_code or gumroad_list_offer_codes, or when a universal vs product-scoped code is appropriate. Usage is only inferable from the tool name.

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