Batch Ozon product details

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

Annotations already declare read-only and idempotent behavior. The description adds useful behavioral context: imageDataUri auto-disables above 24 SKUs and large batches can bloat context. The reload note is ancillary operational guidance but does not conflict with the annotations.

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 three sentences, front-loaded with the core purpose followed by two targeted caveats. The 'Reload MCP after upgrades' note is mildly tangential for tool selection, but the overall description remains tight and readable.

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 description covers batching limits, imageDataUri caps, and context-cost concerns, which is strong. However, with no output schema, it never specifies the shape of a 'product card' or how compact vs rich output differs, leaving some ambiguity for an agent invoking a six-parameter tool.

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 coverage is 100%, so the baseline is 3. The description adds value by linking the payload to nutrition and imageDataUri, and by clarifying that imageDataUri is auto-disabled above 24 products — a behavior stated more explicitly than the schema's 'capped' wording.

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 opens with 'Fetch 1–40 product cards in one call,' naming a specific verb, resource, and batch scope. This clearly distinguishes it from the singular ozon_product_details sibling, and the mention of nutrition and imageDataUri reinforces the card-fetching purpose.

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?

It states when to use the tool (batching 1–40 product cards) and gives an explicit when-not: for huge canvases, prefer a Docker script over stuffing MCP context. However, it does not explicitly route single-card requests to the ozon_product_details sibling, so the alternative guidance is not fully complete.

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