wb_cc_order_meta_delete

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

With no annotations, the description carries the full behavioral burden, but it only restates the destructive action already present in the tool name. It does not disclose irreversibility, idempotency, required permissions, error behavior, or what happens when the key does not exist.

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 one concise sentence with the core action front-loaded. The Russian parenthetical is redundant but harmless and may aid non-English users, so it does not significantly hurt clarity.

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?

This is a simple two-parameter delete operation with no output schema, so a brief description is acceptable. However, without annotations or parameter documentation, the description leaves room for ambiguity about the exact meta key format, return value, and failure modes.

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 0%, so the description must compensate, but it only mentions 'by key' and does not explain the semantics of order_id or the allowed/expected values for key. Some meaning is added by the 'удалить маркировку' hint, but the parameters remain largely underdocumented.

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 ('Delete') and a precise resource ('click-and-collect meta by key'), which clearly distinguishes it from sibling tools like wb_order_meta_delete and wb_dbs_order_meta_delete. The added Russian parenthetical reinforces the meaning ('удалить маркировку' = delete marking).

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 this tool is for deleting click-and-collect order metadata, aided by the 'cc' in the tool name and sibling families like wb_cc_order_meta_get/set. However, it does not explicitly say when to prefer this over wb_order_meta_delete or wb_dbs_order_meta_delete, nor does it state any exclusions.

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