blinkit_add_to_cart

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'reprice' as a side effect, but does not reveal whether the action is reversible, what permissions are needed, or any error conditions. The description is too minimal to fully inform the agent about the tool's behavior.

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 extremely concise, consisting of exactly two short sentences. Every word serves a purpose, with no redundancy or filler. It is front-loaded with the primary action and immediately provides input guidance.

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 add-to-cart tool with one parameter, the description covers the essential action and input source. However, it omits details on what the tool returns (no output schema exists) and the resulting cart state (e.g., whether the cart is now ready for checkout). This leaves some gaps for the agent to infer.

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% (the 'items' parameter has a description). Beyond that, the description adds value by specifying that inputs should come from blinkit_search/blinkit_pick_best, providing context not present in the schema alone. This helps the agent understand the expected data origin.

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 that the tool adds line items to the working cart and reprices. It uses a specific verb ('Add') and resource ('line items to the working cart'), and implies the tool is for adding multiple items. This distinguishes it from sibling tools like blinkit_remove_from_cart and blinkit_clear_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 explicitly tells users to pass product objects returned by blinkit_search or blinkit_pick_best, establishing a clear prerequisite. However, it does not explicitly state when not to use this tool or compare it to other cart-related tools like blinkit_checkout, leaving some room for ambiguity.

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