wb_supply_deliver

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

There are no annotations, so the description carries the behavioral burden. It discloses a meaningful effect: 'tasks move to complete', making clear this is a state-changing action. However, it does not mention reversibility, permissions, or what happens if the action is applied to an already closed supply.

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 with no filler. The key verb, resource, and consequence all appear immediately, and the Russian parenthetical adds minimal clarification without bloat.

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 one-parameter action, the description is mostly sufficient: it states the action and result. But it omits important operational context such as whether the action is irreversible, whether all orders must be included first, or what response or errors to expect. Given no annotations or output schema, this leaves some gaps.

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%, and the description does not explicitly explain 'supply_id'. However, the phrase 'an FBS supply' gives enough context to infer that supply_id identifies the FBS supply to close, partially compensating for the bare schema.

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 and resource: 'Close an FBS supply and hand it to delivery'. It also names the consequence, 'tasks move to complete', which distinguishes it from siblings like wb_supply_delete, wb_supply_create, or wb_supply_detail.

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 gives no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of preconditions such as supply status or readiness. It implies usage through the action but does not help an agent decide between this and the many other supply-related tools.

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