wb_cc_order_meta_get

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

With no annotations, the description carries the full burden of disclosing behavior, but it provides none. It does not say whether the tool reads data, returns metadata, requires permissions, or has side effects; 'meta' alone is an opaque resource label.

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 short and free of filler, but it is under-specified rather than efficiently informative. The Russian parenthetical is redundant, and the one-line noun phrase provides minimal structural 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?

Given the lack of annotations, output schema, and usage guidance, the description is far too minimal. An agent cannot confidently determine what this tool returns, how it differs from other order-meta tools, or what the order_id parameter represents in practice.

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 coverage is 0%, so the description should explain the order_id parameter. It only hints that the ID belongs to a click-and-collect order; it adds no detail about format, semantics, or how the parameter is used.

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 names a specific resource, 'click-and-collect task meta,' which distinguishes it from regular or DBS order meta tools, but it never states the action. The verb 'get' must be inferred from the tool name rather than the description.

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 guidance is given for when to use this tool versus siblings like wb_cc_order_meta_set, wb_order_meta_get, or wb_dbs_order_meta_get. The phrase 'click-and-collect' weakly implies the context, but there is no explicit when-to-use or alternative routing.

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