groupon_view_cart

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description bears less burden. It adds valuable behavioral context beyond annotations by specifying the authentication requirement (GROUPON_SESSION_COOKIE or fetchproxy browser bridge), which is critical for an agent to anticipate failures when no session exists.

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 wasted words. The primary purpose is front-loaded, and the second sentence adds a necessary operational constraint. Every phrase contributes meaning, and the length is proportional to the tool's simplicity.

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 zero-parameter, read-only tool, the description covers everything an agent needs: what it does, what it operates on, and the required session context. No output schema exists, but a cart-view operation's expected response (cart items) is reasonably inferable, and no other operational details are missing.

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 tool has zero parameters, so there is nothing for the description to explain about arguments. The schema fully covers the empty parameter set, and the description appropriately focuses on behavior and prerequisites rather than inventing parameter details.

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 states a specific verb ('View') and resource ('items currently in your signed-in Groupon cart'), making the tool's function immediately clear. It also naturally distinguishes itself from siblings like groupon_purchase and groupon_clear_cart by focusing on viewing rather than modifying the cart.

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 gives clear context for when the tool applies—when a user wants to inspect their current cart—and states the prerequisite session requirement. It doesn't explicitly name alternatives or exclusion conditions, but the purpose is unambiguous given the sibling tool names.

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