groupon_clear_cart

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

While annotations already indicate a mutating operation (readOnlyHint: false), the description adds substantial behavioral context: the dry-run safety mechanism, the removal of every line item, and the post-removal verification that the cart is empty. This goes beyond the structured annotation data.

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 two sentences with no redundant words. It front-loads the primary action and then efficiently explains the two modes of operation.

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 simple one-parameter tool with no output schema, the description covers all essential aspects: purpose, required authentication context (signed-in), the destructive vs. safe modes, and the verification step. It is sufficiently complete for an agent to invoke appropriately.

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 confirm as 'Must be true to proceed... returns a preview', but the description extends this by explaining what the dry run lists and that confirm triggers a re-read to verify emptiness. This adds meaningful behavioral detail beyond the schema's basic preview note.

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's function with a specific verb ('Remove'), a resource ('Groupon cart'), and scope ('ALL items'). It is immediately distinguishable from sibling tools like view_cart (which reads) and purchase (which transacts).

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 provides clear context on how to use the tool safely, explaining the dry-run behavior without confirm:true and the actual removal with confirm:true. It does not explicitly name alternatives, but the usage scenario is obvious and the confirm parameter is thoroughly explained.

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