clear_cart

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

With no annotations provided, the description carries full burden. It discloses that the operation is local and clears both cart and checkout artifacts, which is transparent for a simple tool. It does not specify if there are any irreversible effects beyond clearing, but for a cart-clear operation this is sufficient.

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?

Single sentence with zero wasted words. Front-loads the key action and adds a critical behavioral note. Perfectly 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?

For a zero-parameter tool with an output schema, the description covers the essential behavioral detail (local, no network, clearing cart and artifacts). No further information needed to understand its function.

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?

No parameters exist, so schema coverage is vacuously 100%. The description adds meaning by specifying that it clears 'local cart and checkout artifacts', which clarifies the scope beyond the empty schema.

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?

Description clearly specifies the verb 'clear', the resources 'local cart and checkout artifacts', and a key behavioral qualifier 'no network request is made'. This distinguishes it from sibling tools like add_to_cart or remove_cart_item that involve server interaction.

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 implies the tool is for clearing the cart without a network request, providing clear context. However, it does not explicitly state when to use it over alternatives like remove_cart_item (which removes individual items) or when the local cart is the appropriate choice.

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