wb_supply_trbx_add

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 behavioral disclosure. It reveals that the tool mutates a supply by adding boxes and restricts amount, but it does not explain side effects, prerequisites, reversibility, error behavior, or expected response.

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 a single front-loaded sentence that covers purpose, a parameter constraint, and usage context with minimal redundancy. The Russian parenthetical is unnecessary for English-speaking agents but does not significantly harm 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?

For a mutation tool with no annotations and no output schema, this description under-specifies surrounding context. It does not state what happens after execution, what preconditions exist beyond the brief 'while assembling' note, or how errors are surfaced.

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?

With 0% schema description coverage, the description must compensate for both parameters. It clarifies that amount is a box count limited to 1..1000 and that supply_id identifies the target supply, but it omits format details and leaves supply_id semantics mostly to inference from the tool name.

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 action ('Add boxes') on a specific resource ('a supply') and adds constraints: amount 1..1000 and pickup-point-only while assembling. This makes the tool easily distinguishable from siblings like wb_supply_trbx_delete or wb_supply_add_orders.

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 phrase 'pickup points only while assembling' gives a usable condition for when this operation is appropriate. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to avoid using it in obviously wrong situations.

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