wb_cc_order_meta_set

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 disclosing side effects. It implies mutation through 'set' and 'status confirm' but does not state whether existing values are overwritten, what order statuses are affected, what validation applies, or what the success/failure response looks like. This is insufficient for a state-changing 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 compact and front-loaded with the core purpose and accepted meta types. However, 'status confirm' is a cryptic fragment, and the Russian translation largely repeats the English phrase, so brevity is achieved at the cost of 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?

Given that there is no output schema and no annotations, the description is incomplete: an agent cannot confidently infer the expected value payload, mutation side effects, or response behavior. It covers only the domain and meta_type enumeration, leaving important call requirements unspecified.

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 only 33%, so the description needed to compensate. It repeats the meta_type enum values but adds no real meaning for order_id or the content and format of value beyond the schema's 'sgtin: array; others: string'. The value payload semantics remain ambiguous.

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 identifies the resource (click-and-collect order meta), the operation (marking/set), and enumerates the accepted meta types (sgtin|uin|imei|gtin). The phrase 'status confirm' is vague, but the core purpose is distinguishable from the sibling get/delete tools by the click-and-collect context and 'set' operation.

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?

No explicit when-to-use or when-not-to-use guidance is provided, and no alternative sibling tools are mentioned despite the presence of wb_cc_order_meta_get, wb_cc_order_meta_delete, and wb_dbs_order_meta_set. The only usage signal is 'click-and-collect marking', which forces the agent to infer applicability.

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