groupon_purchase

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

The description discloses key behaviors beyond the readOnlyHint: it previews changes without confirm, re-reads the cart after adding, returns a checkout URL, and cannot complete the order. These are not implied by the annotations and significantly inform the agent.

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 three sentences long, front-loaded with the main purpose, and presents the dry-run/confirm logic and limitation clearly without redundant phrases.

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 tool has moderate complexity with a dry-run mode and required confirmation, but the description covers the behavior, the return value (checkout URL), and the payment constraint. It also directs users to groupon_get_deal for optionId, making it sufficiently complete given the schema richness.

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 the schema already explains all five parameters. The description adds context about the dry-run/confirm flow, but doesn't add per-parameter details 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 'Add a Groupon deal option to your cart', clearly identifying the action and resource. It distinguishes itself from sibling tools like search and view_cart, and explicitly states it cannot place the order.

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 explains the dry-run vs confirmed execution modes ('WITHOUT confirm:true this is a DRY RUN... WITH confirm:true it adds the item...'), and clarifies that payment is completed externally. It also notes the limitation ('It CANNOT place the order') and points to native checkout as an alternative.

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