ozon_report_discounted_create

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 restates the report subject and neither explains whether this creates an asynchronous report job nor what the response contains, leaving the side effects and output behavior completely 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 description is short, but it is under-specified rather than concise: 'Report on discounted goods (отчёт по уценке)' is essentially a bilingual label, with the Russian phrase adding no new information. It spends no words on the operation, output, 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?

For a create-report tool with no output schema, no annotations, and closely related report siblings, the description is too thin. It omits what the tool returns, whether the report is generated synchronously, and how the result could be retrieved via report_info or report_list, so an agent cannot fully anticipate the call's outcome.

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 input schema has zero properties, so there are no parameters that need explanation; the 0-param baseline applies. The description's subject mention ('discounted goods') is consistent with the tool doing a single fixed operation with no arguments.

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 names the resource ('discounted goods' / 'уценка') and thereby distinguishes this from reports on products, stocks, or finance. However, it is a noun phrase with no verb, so it never explicitly states that the tool creates or generates a report; the action must be inferred from the tool name.

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 or how it relates to sibling tools like ozon_report_products_create, ozon_report_list, or ozon_report_info. It gives no context about prerequisites, async report generation, or follow-up steps, so an agent cannot learn the intended workflow from the description.

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