Очистить корзину

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

No annotations are provided, so the description carries the full burden of disclosure. It explicitly states the destructive nature (clears all items and all carts) and explains that Yandex Eda does not allow editing cart options, which sets expectations for the replacement workflow. This is rich behavioral context beyond simple read/write.

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?

Two sentences, front-loaded with the primary action (clearing the cart) followed by usage alternatives. Every sentence adds crucial information without fluff or redundancy. Efficient and well-structured.

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 parameter-less, no-output-schema destructive operation, the description fully covers purpose, scope, and usage alternatives. It also explains a platform limitation (no option editing) that affects how the tool should be used, making it complete for an AI agent.

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, and the schema trivially covers all of them. Per the baseline rule, a score of 4 is appropriate for zero-parameter tools. The description adds meaningful context about the scope (all items and all carts), which is valuable even without parameters.

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 states 'Полностью очищает корзину (ВСЕ позиции и все корзины)' – a specific verb and scope. It distinguishes itself from remove_from_cart by indicating it clears all items, not just one, and clarifies that this tool clears all carts.

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?

Explicitly directs the agent to use remove_from_cart when only one item needs changing, and provides a workflow for changing options: remove_from_cart (or clear_cart if only one item) followed by add_to_cart. This gives concrete when-to-use and when-not-to-use guidance.

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