ozon_warehouse_list

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. It only names the resource and gives no indication of side effects, return format, pagination, or whether this is a simple read of warehouse metadata.

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 this is under-specification rather than conciseness. It omits a verb and any substantive detail, resembling a label more than a tool definition, similar to the 'Process' calibration example.

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 and no output schema, the description should explain what kind of data is returned and in what context it is useful. The current definition provides only a nominal subject and fails to give the agent enough context to confidently invoke it.

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 100%; the 'view' parameter is already documented with an enum and explanation of compact vs full behavior. The tool description adds no additional parameter semantics, which is acceptable at the baseline for complete schema coverage.

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 ('Seller FBS warehouses') but is a noun phrase rather than a statement of action. The verb 'list' is only present in the tool name, and the description does not distinguish this from sibling tools like ozon_stock_on_warehouses that also concern warehouses.

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, when not to use it, or how it relates to alternatives such as ozon_stock_on_warehouses or ozon_product_stocks_by_warehouse. The agent is left to infer usage solely from the name.

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