ruddur_update_coupon

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

Annotations already indicate a non-read-only, non-idempotent, non-destructive operation; the description adds that the server accepts specific coupon aliases and requires marketplace.manage scope. It does not discuss merge vs. replace semantics or response shape, but the annotation coverage lowers the bar.

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 sentences, front-loaded with the action, and each clause adds value (purpose, aliases, scope requirement). No redundancy or filler.

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 mutation tool with a generic body and no output schema, the description provides the essential operation, authorization scope, and accepted field aliases. It stops short of explaining update semantics, error cases, or return values, but combined with 100% schema coverage and annotations, it is reasonably complete.

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%, so baseline is 3. The description supplements the generic body schema by enumerating accepted coupon aliases (promoCode, percentOff, amountOff, expires, usageLimit, marketplaceListingId), which adds practical meaning. It does not detail how aliases map to body/query fields, but it goes beyond the schema.

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 opens with 'Update a marketplace coupon,' a specific verb+resource pairing that clearly distinguishes this from sibling tools like ruddur_create_coupon and ruddur_list_coupons. The alias list adds further operational specificity.

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?

Usage is implied: use when updating an existing marketplace coupon, reinforced by the 'Requires scope: marketplace.manage' prerequisite. However, it does not explicitly contrast with ruddur_create_coupon or other coupon tools, and there are no when-not-to-use/exclusion statements.

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