wb_supply_barcode

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

With no annotations provided, the description carries full behavioral burden, but it only says the tool provides a QR code. It does not disclose whether the operation is read-only, what output format is returned, whether barcode_type affects the response, or any authentication or side-effect considerations.

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 short sentence with no filler and the core purpose is front-loaded. It is concise, though slightly too sparse to fully compensate for the missing parameter documentation.

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 tool with no annotations, no output schema, and zero parameter description coverage, this description is incomplete. It leaves important details unresolved, such as what the QR code output looks like, what barcode_type values are supported, and how this tool relates to the many barcode/sticker/supply siblings.

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%, so the description must compensate for undocumented parameters. It indirectly clarifies supply_id by referencing an FBS supply, but barcode_type is not explained anywhere — no mention of supported formats, defaults, or expectations.

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 (FBS supply) and the intended use case (warehouse handover QR code), which is reasonably specific and differentiates it from generic barcode or supply-list tools. It lacks an explicit verb like 'generate' or 'retrieve', but the phrase 'QR code' makes the intent understandable.

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 'for warehouse handover' gives an implied usage context, suggesting this tool is appropriate when preparing a supply QR code for the warehouse. However, it does not mention when to avoid this tool or point to any alternative sibling like wb_barcodes_generate or wb_supply_detail.

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