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

Annotations already declare this is a non-read-only, non-idempotent mutation, so the description does not need to re-explain mutation. It adds useful context about batched execution via `accepts ids`, but it does not describe return values, side effects, permissions, or what happens after duplication beyond the action name.

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 short and front-loads the generic mutation context, but it repeats several unrelated actions (create, update, delete, set_activation) before narrowing to `duplicate`. It is not bloated, yet some text could be trimmed to focus more directly on the single flattened action.

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?

The description is minimal and incomplete for safely invoking the tool: there is no required-parameter guidance, no explanation of `account`, no clear role for `data`, and no description of the result or error behavior. A duplication tool with 4 parameters and no output schema needs more detail than this.

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%, so the description needs to compensate for all four parameters. It clarifies `id` and `ids` reasonably through `duplicate(id)` and bulk support, but `account` and `data` are not explained in the context of this duplicate tool.

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 clearly identifies this as a mutation tool for Guru coupons and includes `[Flattened action: duplicate]` plus `duplicate(id)`, so an agent can see this is the duplicate operation. However, the generic action list also mentions create/update/delete/set_activation, which somewhat dilutes the singular focus and makes sibling differentiation less crisp.

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 implies when to use the tool through `duplicate(id)` and bulk support with `ids`, giving useful operational context. However, it does not explicitly say when to prefer this over sibling actions like `guru_coupons_write_create` or `guru_coupons_write_update`, and there are no exclusions or alternative-tool recommendations.

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