wb_supply_detail

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. 'Info' implies a non-destructive read operation, but the description does not mention authentication needs, rate limits, error behavior, or what happens for invalid supply IDs.

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 extremely short and free of fluff, but it is under-specified rather than appropriately concise. A one-line fragment without a verb or additional context does not satisfy the structure expected for a usable tool description.

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?

The tool is simple with a single parameter, but with no output schema and no behavior notes, the description leaves important gaps. An agent can infer it returns FBS supply details, but it does not say what those details are or how to obtain a valid supply_id.

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 0% description coverage for supply_id, and the description adds no explanation of the parameter's format, source, or relationship to other supply endpoints. The name is somewhat self-explanatory, but the description does not compensate for the missing schema-level guidance.

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 as FBS supply information, which helps distinguish it from FBW supply tools, and the Russian phrase 'детали поставки' reinforces that it returns supply details. However, it is a noun phrase rather than a verb-driven statement, and it essentially restates the tool name without specifying what details are included.

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?

There is no guidance on when to use this tool versus related siblings such as wb_supplies_list, wb_supply_order_ids, or wb_fbw_supply_detail. No prerequisites, exclusions, or alternative-selection criteria are provided.

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