ozon_fetch_all

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

Annotations already mark readOnlyHint=true, so the safety profile is covered. The description adds substantial behavioral detail: it handles multiple pagination styles, automatically detects the array path, manages cursor fields, enforces a max_items cap to protect context, and returns a structured result with a 'truncated' flag. This gives the agent a clear model of what will happen during execution.

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 well-structured and front-loaded: a one-sentence purpose, a brief pagination-support note, then a clean Args list and return shape. There is no filler, and every sentence earns its place.

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 tool with 7 parameters, the description provides enough operational detail to invoke it correctly: purpose, pagination behavior, parameter roles, defaults, and return envelope. Since an output schema exists, return values are even less burdensome. It omits explicit error-handling and rate-limit expectations, but these are outweighed by the strong parameter and behavior coverage.

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 carries the full burden for clarifying parameters. The Args section meaningfully explains operation_id, query/body/path_values as base parameters with cursor fields managed, items_path as an override, limit as page size, and max_items as a hard cap. It covers all parameters, though query/body/path_values are grouped and could be more granular about how each is used.

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 'Auto-paginate a read endpoint and return every row in one response,' which names a specific action, resource, and scope. It clearly distinguishes itself from sibling single-call tools like ozon_call_method by emphasizing automatic pagination across all rows and by listing supported pagination styles.

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 makes the use case clear: use this when you need all rows from a read endpoint, rather than making manual paginated calls. It also states that cursor fields are managed, so callers should not pass them. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of fully explicit routing guidance.

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