wb_warehouses

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

No annotations are provided, so the description alone must disclose behavior. It states only what the resource is, not what the operation does, whether it is read-only, what data it returns, or any side effects. This is insufficient for safe invocation.

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, but brevity here comes at the expense of necessary information. It is under-specification rather than effective conciseness, lacking any actionable verb or usage context.

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?

Although the tool has a trivial empty schema, the description is not complete enough for an agent to call it correctly. There is no output schema and no annotations, so the description should at minimum say that it returns seller warehouses or lists available warehouses. As written, it leaves the operation ambiguous.

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 tool has zero parameters and the input schema is fully described as empty, so there is no parameter documentation burden on the description. The baseline of 4 applies because there are no parameters for the description to clarify or compensate for.

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 "Seller warehouses (склады продавца)" is a noun phrase that essentially restates the resource named by the tool. It names the subject but provides no verb or action, so an agent cannot tell whether this tool lists, retrieves, or manages warehouses. It only weakly hints at being the read/list counterpart to wb_warehouse_create/update/delete.

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 about when to use this tool versus alternatives such as wb_warehouse_remains, wb_fbw_warehouses, or the warehouse CRUD siblings. No context, exclusions, or alternative routing is given, leaving the agent to guess which of many warehouse-related tools is appropriate.

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