add_flash_deal_to_cart

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

No annotations are provided, so the description carries the full burden. It discloses that the price is always 0, requires authentication, has a default flashDealId, and includes a clear error-handling flow (call get_flash_deal_status on eligibility failure to diagnose). It doesn't describe the success return value, but that is a minor gap for a cart-add tool.

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 a single paragraph with several distinct instructions, all relevant and front-loaded with the primary purpose. It is slightly verbose but every sentence earns its place, so it remains concise.

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?

Covers purpose, alternatives, parameter sourcing, error handling, and authentication. The only missing piece is a description of the success response, but given the tool's simplicity and lack of output schema, this is a minor omission.

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 coverage is 100% with each parameter described. The description adds extra context beyond the schema by specifying that productId comes from get_flash_deals and that flashDealId defaults to 11732, reinforcing the 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 explicitly states 'Add a Mega Flash Deal product to the cart for free' with a specific verb and resource, and clearly distinguishes from the sibling add_to_cart by saying to use this instead for flash deal items.

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?

Provides explicit when-to-use guidance: 'Use this instead of add_to_cart for flash deal items' and when not to use get_flash_deal_status: 'Do NOT call get_flash_deal_status before every add — only use it to explain a failure.' This clearly maps alternatives and exclusions.

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