wb_cc_orders_new

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states a noun phrase and reveals nothing about whether the tool is read-only, what it returns, how 'new' is determined, or any side effects. This is essentially a label, not a behavioral description.

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 very short and contains no filler, which is concise. However, it is a fragment rather than a complete sentence and lacks structural clarity such as an action verb. The redundant Russian translation provides little additional value.

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?

There is no output schema, no annotations, and no explicit statement of what the tool does or returns. The description leaves the agent to infer that this lists or retrieves new click-and-collect tasks, which is insufficient for unambiguous invocation, especially given the large family of sibling cc-order tools.

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 input schema has zero parameters, so the baseline is 4. The description adds nothing about parameters, but none exist, so there is no gap to compensate for.

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 a resource ('new click-and-collect tasks') and a scope ('new'), which helps distinguish it from wb_cc_orders. However, it lacks an explicit verb such as 'get', 'list', or 'retrieve', so the intended action is only inferred from the tool name and the noun phrase.

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 provides no guidance on when to use this tool versus alternatives like wb_cc_orders, wb_cc_orders_status, or wb_dbs_orders_new. There is no mention of contexts, prerequisites, or exclusions; usage is only weakly implied by the word 'new'.

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