ozon_product_discounted

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only info operation but does not describe what is returned, whether side effects occur, or any authorization requirements. The word 'info' is the only behavioral hint.

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 a single compact sentence with no filler. It is appropriately short, though the ambiguity of 'Markdown' slightly undermines clarity.

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 output schema and no annotations, the description should explain what the agent can expect back. It only states the subject area, leaving return format, handling of empty/invalid SKUs, and interaction with related discount workflows undocumented.

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%, so the description must compensate, but it only echoes the parameter concept ('discounted SKUs') without explaining what the integers represent, how SKU identifiers should be formatted, or any constraints. The parameter name is self-descriptive, but no additional semantic value is provided.

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 SKUs') and the type of data ('Markdown info'), which is more than a tautology, but it lacks a verb and uses 'Markdown' ambiguously (discount/markdown vs. Markdown formatting). It does not differentiate this tool from numerous sibling discount-related 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?

No guidance is given about when to use this tool versus alternatives like ozon_discount_tasks, ozon_discount_approve, or ozon_report_discounted_create. An agent is left to infer the appropriate context from the name and description alone.

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