Browse Ozon seller catalog

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds return-field behavior ('same fields as ozon_search items plus seller info') and filter support, but doesn't disclose pagination behavior or compact/rich output effects beyond what the schema conveys.

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 compact and front-loaded: purpose, usage condition, and return/filter capabilities each get one sentence. No sentence is redundant or wasted.

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 read-only listing tool, the description provides the core purpose, use condition, return-field relationship, and filter capabilities. It lacks an explicit output schema and relies on knowledge of ozon_search fields, but the annotations and input schema cover safety and required parameters well.

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?

With only 43% schema description coverage, the description partly compensates by mentioning 'sort and price filters', which maps to the sort, priceMin, and priceMax parameters. However, it doesn't explain limit semantics or the compact/rich distinction, leaving some parameter meaning to the schema and parameter names.

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 a specific resource ('seller's shop page') and the action ('product listing', 'what else this shop sells'). It differentiates from siblings by noting it returns the same fields as ozon_search items plus seller info, making the tool's scope and output relation clear.

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 gives an explicit triggering condition: 'Use when user wants to see what else this shop sells.' This provides clear context for when to select this tool, though it doesn't explicitly name alternatives or state when not to use it.

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