Create discount

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation/safety profile is covered structurally. The description adds nothing beyond that — no note that creation is non-idempotent (repeated calls may create duplicate codes), no store/account scoping requirement, no confirmation expectation.

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?

It is short, but this is under-specification rather than conciseness. The single sentence carries no actionable information for an agent facing an 18-parameter nested body.

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, non-idempotent, open-world mutation with 18 parameters, nested objects, mutually exclusive body-input modes, and no output schema, the description is wholly inadequate. It omits required payload shape, store relationship binding, and confirmation behavior.

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?

18 parameters with only 22% schema description coverage, including an empty-description 'code' and 'name', a nested JSON:API 'payload'/'payload_file' mutually exclusive pair, and a 'confirm' flag whose semantics live only in the schema. The description supplies zero parameter meaning, so it fails to compensate for the coverage gap.

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 is 'Create a discount.' — a verbatim restatement of the tool name and title with no added detail. It does not distinguish this tool from delete_discount, get_discount, list_discounts, or list_discount_redemptions, all of which are siblings an agent must choose between.

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?

No when-to-use guidance, no prerequisites, no mention of alternatives. The description does not explain when a discount should be created versus updated or deleted, nor does it reference the 'confirm' parameter's intent that actions be explicitly requested.

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