discount_update

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

Adds context beyond annotations: partial update requirement (at least one field must be supplied) and enum validation ('client-validated'). No contradiction with annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true).

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?

Single sentence with all key information: action, HTTP method, envelope, partial requirement, enum restrictions. Front-loaded and efficient.

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 partial update and enum restrictions well. Lacks details on other optional fields, but given schema provides names and types, it is reasonably complete for a mutation tool with no output schema.

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?

Lists enum values for status, amount_mode, discount_type, applies_to, adding 'client-validated' context. However, schema coverage is 0%, and description does not explain other parameters like site, discount_id, code, etc. Only partial compensation for enum fields.

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?

Clearly states 'Update a discount' with HTTP method, partial update requirement, and lists enum-restricted fields. Differentiates from sibling tools like discount_create and discount_delete.

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?

Implies usage for updating existing discounts with partial updates, but does not explicitly state when to use or exclude alternatives. No mention of prerequisites or conditions.

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