Autoload: upload listings

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

Annotations already include readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds that it is read-only with pagination and returns meta with total/pages. No contradiction with 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?

Two concise sentences: first covers purpose and output, second provides usage guidance and cross-reference. No redundant or irrelevant content.

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?

Given the 5 parameters, no output schema, and existing annotations, the description is complete. It specifies the returned fields, pagination behavior, and links to related tools for context.

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 100%, so baseline is 3. The description adds minimal extra information beyond schema; it mentions getting sections from report's section_stats, which is already in the schema description for the sections parameter. No significant additional meaning.

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 clearly states the tool returns processing results of each listing in a specific upload by report_id, listing fields like ad_id, avito_id, avito_status, errors/warnings, and a link. It identifies the resource (processing results) and action (returns), and distinguishes from the summary tool autoload_get_report_by_id_v3.

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?

Explicitly states when to use: for a line-by-line breakdown of an upload, and when not: for an upload summary use autoload_get_report_by_id_v3. Also tells how to get sections filtering from report's section_stats.

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