ozon_pricing_strategy_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 behavioral disclosure. It does not mention that this is a read-only list operation, what data is returned, whether pagination applies, or any side effects. The Russian parenthetical adds no behavioral transparency.

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 and free of fluff, but it under-specifies the operation: it explains what pricing strategies are, not what the tool does. The Russian gloss is not useful for an agent deciding how to invoke the tool.

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 simple two-parameter list operation with no annotations and no output schema, the description should at least say 'list all pricing strategies' and note pagination behavior. Instead it offers only a domain definition, leaving the agent to infer the operation from the tool name and sibling context.

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 needed to compensate for the page and limit parameters, but it does not mention them at all. The schema provides only parameter names and defaults; the description adds no meaning about pagination or result limits.

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 the resource as 'pricing strategies' and explains the domain ('auto price management against competitors'), but it never states that the tool lists or retrieves strategies. The verb 'list' is only supplied by the tool name, and the description does not distinguish this list operation from sibling pricing-strategy 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 on when to use this tool versus alternatives such as ozon_pricing_strategy_info, ozon_pricing_strategy_status, or ozon_pricing_competitor_prices. The description only defines the domain concept and provides no use-case context, exclusions, or alternatives.

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