ozon_product_info

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It does not state side effects, read-only status, return behavior, authorization needs, or any other operational characteristics.

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 Russian translation is redundant and the phrase as a whole is under-specified rather than efficiently informative. A small amount of added detail such as 'returns full product details for the given product IDs' would be more valuable.

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 no output schema and no annotations, the description must explain what the tool returns and when to use it. It fails to mention what 'extended product info' contains, whether multiple IDs are supported beyond the schema, or how it differs from other product information tools in the sibling list.

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 adds no meaning to the single product_id parameter. It does not explain expected array size, what constitutes a valid product ID, or how the parameter relates to the returned information.

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 'Extended product info (информация о товарах)' is essentially a restatement of the tool name with the modifier 'extended'. It names a resource but lacks a verb and any concrete indication of what specific product data is returned, making it a vague purpose rather than a clear definition.

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?

The description provides no guidance on when to use this tool versus alternatives. Among dozens of sibling product-related tools such as ozon_product_list and ozon_product_attributes, nothing explains what makes this the right choice.

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