Autoload: upload listings

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

Annotations already provide readOnlyHint=true and idempotentHint=true, and the description reinforces read-only behavior. It adds details about pagination (response contains meta with total/pages). No contradictions. Slight additional value beyond annotations, but could mention more about response format or error states.

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 concise (two sentences plus an additional usage guideline sentence) and front-loaded with the core purpose. No unnecessary words. Every sentence adds value.

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 5 parameters and no output schema, the description covers purpose, output fields, pagination, and usage. It references where to get report_id and section slugs. Missing details about what exactly is in the 'link' and error handling, but overall complete for a read-only tool with good annotations.

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%, but the description adds context: for report_id it says 'obtain it via autoload_get_reports_v2', for sections 'get the slugs from the report's section_stats (e.g. via autoload_get_report_by_id_v3)'. It also clarifies default values for page and per_page, and how query and sections accept comma or pipe separators. This significantly enhances parameter meaning beyond the schema.

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 it returns processing results of each listing in a specific upload by report_id, listing specific fields (ad_id, avito_id, etc.). It also mentions read-only and pagination. This distinguishes it from its sibling autoload_get_report_by_id_v3 by focusing on line-by-line breakdown vs summary.

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 'Use it for a line-by-line breakdown of an upload; for an upload summary see autoload_get_report_by_id_v3.' This directly addresses when to use this tool and provides a clear alternative. It also gives guidance on obtaining section slugs from the report's section_stats, showing how to use the sections filter.

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