ozon_supply_order_timeslots

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 explaining behavior. 'Available timeslots' hints at a read-only query, but the description does not explicitly state what the tool returns, whether it has side effects, or any constraints such as expiry or availability.

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 short and front-loaded with the main concept, with no filler. However, it is a noun phrase rather than a clear instruction, and it omits the crucial relationship to the required supply_order_id parameter.

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?

Given that there is no output schema, no annotations, and 0% schema description coverage, the description is too thin. It does not explain the return shape, how the supply_order_id is used, or any prerequisite context needed to call the tool correctly.

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%, and the description does not explain the required supply_order_id parameter or how it relates to the returned timeslots. The parameter name is somewhat self-explanatory, but the description adds no semantics beyond the schema.

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 a specific resource — FBO supply timeslots — and distinguishes it from sibling tools like ozon_supply_orders or ozon_supply_order_get. However, it lacks an explicit verb such as 'list' or 'get', so the operation is implied rather than stated.

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 versus alternatives. It does not mention that it applies to a specific supply order, nor does it contrast with sibling tools like ozon_supply_order_get or ozon_supply_order_counters.

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