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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the endpoint (GET /provider/coupons) and the shape of the returned fields, but says nothing about auth requirements, rate limits, or pagination behavior beyond what the schema documents. With annotations carrying the safety burden, a 3 is appropriate.

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?

A tight two-sentence entry with the resource and returned fields front-loaded; nothing is padded. The trailing 'GET /provider/coupons' is a minor addition of limited value to an agent, keeping it just below a perfect score.

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?

With no output schema, the description usefully enumerates the fields returned by a coupon, and the annotations cover the safety profile while the schema covers pagination and filters. It is close to complete for a simple read-only list tool, missing only notes on default filtering/sorting 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 100%, so all four parameters (limit, offset, archived, redeemable) are fully documented in the schema. The description's phrase 'redeemable window and archive state' gestures at the redeemable/archived filters but adds no syntax or default behavior beyond the schema. Baseline 3 applies.

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?

States a specific verb ('List') and a specific resource ('membership coupons'), then enumerates the returned fields (code, discount, duration, redeemable window, archive state). Among siblings that all list other resources (invoices, patients, plans), 'coupons' is unambiguous and the agent can select it without opening the schema.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives or the conditions under which this listing should be preferred. Usage is only implied by the name and resource.

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