ozon_supply_orders

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

With no annotations, the description carries the burden of behavioral disclosure, but it only says the tool returns order_ids. It does not state pagination behavior, response shape, whether it is read-only, or how states filter behaves, leaving a meaningful transparency gap.

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 compact and front-loads the core purpose and the key sibling pointer. Even though it is minimal, it is a single efficient sentence with no filler.

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 list operation with no output schema, no annotations, and minimal parameter documentation, the description is incomplete. An agent would still need external knowledge about Ozon supply order states, pagination, and response format to invoke it confidently.

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 coverage is 50%, and the description names 'states' only indirectly as 'status codes 1-8' via the schema but does not add meaning about how filtering works. The limit parameter is entirely unrepresented in the description, so the description contributes little beyond what the schema already says, though the schema itself is reasonably clear.

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 clear action ('returns order_ids') and identifies the resource ('FBO supply orders (v3)'), and it points to ozon_supply_order_get for details, distinguishing it from the get-one sibling. However, it is brief and leaves some ambiguity about what the overall list function actually returns beyond IDs.

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 description implies use for listing FBO supply orders and explicitly references ozon_supply_order_get for detail retrieval, giving some routing guidance. It does not explain when to prefer this over ozon_supply_order_counters or ozon_supply_order_timeslots, so guidance is partial.

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