coupon_clipped

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

Annotations already declare readOnlyHint=true, so the description carries a lower burden. It adds value by explaining that clipped coupons automatically apply at checkout and that it returns all clipped coupons. This contextualizes the behavior beyond the annotation.

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?

Three sentences, front-loaded with the core purpose. Every sentence adds value without redundancy. Efficient and clear.

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?

Given the simplicity (one optional parameter, output schema exists, annotations present), the description is largely complete. It explains what clipped coupons are and their behavior at checkout. Could mention pagination or ordering, but not required for minimal viability.

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 coverage is 100% for the single 'limit' parameter, so baseline is 3. The description does not mention the limit parameter or add any additional meaning beyond the schema. No deduction needed, but no extra credit.

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 states the tool lists clipped coupons (specific verb+resource). It distinguishes from siblings like coupon_clip, coupon_list, and coupon_search by focusing on already-clipped coupons. The additional context about auto-apply at checkout adds clarity.

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 usage when you want to view clipped coupons. It does not explicitly state when not to use or mention alternatives, but the purpose is clear enough given sibling names. Adding a note about using coupon_search for finding new coupons would improve guidelines.

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