ozon_product_limits

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only provides a label. It does not state whether the call is read-only, whether it has side effects, what the response contains, or if any seller permissions are required. This is not a behavioral description at all.

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 one short sentence and wastes no words, which is concise. However, it is more of a title than a functional description, and the brevity does not compensate for the missing verb and context. It could be much more helpful at the same length with a verb and one clarifying detail.

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?

The tool has no parameters and no output schema, so the description is the agent's only source of context. It names the topic, product creation limits, but does not say what the output looks like, what the limits mean, or when an agent should prefer this over other product tools. This is not enough for reliable selection and invocation.

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 tool has zero parameters and an empty input schema, so there are no parameter semantics for the description to clarify. Per the guideline that 0-parameter tools receive a baseline of 4, this dimension is adequately handled by the schema. The description adds nothing about parameters, but nothing is needed.

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 is a noun phrase, not a verb phrase; it never states whether the tool gets, lists, or updates product creation limits. 'Product creation limits (лимиты товаров)' essentially restates the tool name 'ozon_product_limits' in English and Russian. It identifies the resource but not the operation, leaving the agent to guess what calling it accomplishes.

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 related siblings like ozon_product_list, ozon_product_info, or ozon_diagnostics. No triggers, exclusions, or alternative routing hints are provided. The agent must infer the tool's role entirely from its name.

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