groupon_view_cart

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

Annotations already declare readOnlyHint=true, and the description adds valuable behavioral context by specifying the session requirements: 'GROUPON_SESSION_COOKIE, or the fetchproxy browser bridge signed into groupon.com.' This goes beyond the annotation's safety read-only indication.

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 long, front-loaded with the core action, and every word adds value. It is concise without omitting important prerequisite 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?

For a simple view operation with no parameters and no output schema, the description adequately covers what it does and prerequisites. It could mention response format (e.g., list of items), but the tool's simplicity makes it less critical.

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?

There are zero parameters, so the schema is trivially covered. The description correctly avoids inventing parameter details, and there is no need for additional parameter semantics.

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 and resource: 'View the items currently in your signed-in Groupon cart.' This clearly distinguishes it from sibling tools like groupon_clear_cart and groupon_purchase, which have different actions.

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 indicates a prerequisite: 'Requires a Groupon session (GROUPON_SESSION_COOKIE, or the fetchproxy browser bridge signed into groupon.com).' It provides context for when this tool is usable, though it does not explicitly mention alternatives or when not to use it.

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