update_discount

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

There are no annotations, so the description carries the full behavioral disclosure burden. It only says the tool updates an existing discount, but it does not clarify whether the update is partial or full replacement, whether changes affect active checkouts, what permissions are needed, or what side effects may occur.

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 with no filler. It is appropriately concise, though it achieves conciseness at the expense of substantive guidance.

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 six-parameter mutation tool with no annotations and no parameter-level schema descriptions, this description is too thin. The output schema partially covers return values, but the description lacks behavioral context, usage guidance, and parameter semantics, leaving an agent to guess at important update 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?

Schema description coverage is 0%, and the description names none of the six parameters. An agent gets no additional meaning beyond the raw parameter titles like 'Amount Off' or 'Percent Off', so it cannot confidently decide which optional fields to provide or how they interact.

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 states a clear verb and resource: 'Update an existing discount or promotional code.' This directly distinguishes it from sibling tools like create_organization_discount, delete_discount, and get_discount, since only this tool handles updates.

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 gives no explicit guidance about when to use this tool versus alternatives. It implies it is for existing discounts by using the word 'existing', but it does not mention that create_organization_discount should be used for new discounts or that get_discount should be used for retrieval.

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