coupon_clip

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

Beyond the annotations (destructiveHint: true), the description adds important behavioral context: preview mode without confirm, authentication requirement for confirm, and automatic application at checkout. This fully informs the agent of the tool's effects and prerequisites.

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 concise sentences front-load the purpose and then explain the two modes and outcome. No redundant or extraneous information.

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 tool's low complexity (2 parameters, one required) and the presence of an output schema, the description covers the essential workflow: preview vs. confirm, authentication, and automatic checkout application. It is complete for the agent to use correctly.

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?

The schema already describes parameters, but the description adds critical context: coupon_id should come from coupon_list or coupon_search, and confirm toggles between preview and actual clip. This meaningfully extends beyond the schema descriptions.

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 verb 'Clip' and resource 'coupon to your HEB account', distinguishing it from sibling tools like coupon_list (listing) and coupon_search (searching). It also explains the dual behavior with preview mode.

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 clearly explains when to use confirm=false (preview) and confirm=true (clip, requires authentication). It does not explicitly state when not to use or mention alternatives, but the context from siblings and the explanation of preview versus actual action provides sufficient guidance.

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