wb_document_download

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

No annotations are provided, so the description carries the full behavioral burden. It clearly communicates a read-only fetch operation, exactly one document, and the two supported output formats. It does not describe error behavior or response packaging, but for a simple download operation no destructive or state-changing behavior needs to be disclosed.

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: action, resource, formats, and selector all appear immediately. The parenthetical Russian translation is the only minor extra, but it does not meaningfully reduce 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 low-complexity, one-parameter tool with no output schema, the description is mostly sufficient: it states the action, scope, formats, and ID requirement, while the schema ties the ID to wb_documents_list. It could be slightly more complete by explicitly pointing to wb_documents_list as the source of valid IDs and naming the bulk sibling, but nothing essential to invoking the tool is missing.

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 schema already documents the sole parameter at 100% coverage with 'document id from wb_documents_list'. The description only restates that the download is by ID and adds nothing new about the parameter's meaning, format, or constraints. Baseline 3 is appropriate when the schema fully handles parameter documentation.

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 ('Download'), a direct object ('one document'), supported formats ('PDF/XML'), and the selector ('by ID'). The word 'one' clearly differentiates it from the sibling wb_documents_download_bulk, so an agent can distinguish the tool without opening the schema.

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 singular phrasing 'one document' and 'by ID' imply the intended use case, but the description does not explicitly say when to prefer this tool over wb_documents_download_bulk or wb_documents_list, nor does it state when not to use it. Guidance must be inferred rather than stated.

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