ozon_report_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 disclosing behavior. It only says 'Generated reports' and gives no information about side effects, permissions, pagination behavior, return shape, or whether the operation is read-only. The runtime behavior is essentially opaque.

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 text is short, but the brevity is under-specification rather than useful conciseness. It is a label-like phrase with no operational content, so there is almost nothing for an agent to act on.

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?

With two parameters, no output schema, and no annotations, the description leaves nearly everything to inference. It does not explain what generated reports are included, how filter or pagination works, what the response looks like, or how this tool relates to the many sibling report tools.

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 mention the 'page' or 'report_type' parameters at all. An agent cannot infer how pagination works, what values report_type accepts, or how these parameters affect the returned list.

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 'Generated reports (список отчётов)' indicates that the tool deals with a list of reports, so the general purpose is somewhat clear. However, it is a noun phrase rather than an explicit verb+resource statement, and it does not differentiate this list operation from siblings like ozon_report_info or the report creation tools.

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 ozon_report_info, ozon_report_products_create, or ozon_returns_report. The description merely names the resource and gives no selection criteria, exclusions, or context about which report-related task it belongs to.

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