Workbooks List Report Pages

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

Annotations already declare a safe read, but the description adds genuinely new behavior: it auto-paginates to the last page and normalizes nextPageToken to null, implying a full multi-request fetch and potentially costly call. This is real disclosure beyond the annotation set, though it omits any failure/empty-report behavior.

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 tight sentences, the primary action front-loaded, and the pagination explanation earns its place by explaining the always-null nextPageToken. Minor redundancy between 'follows pagination to the last page' and 'every page is read'.

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?

With an output schema and full annotations, the definition covers safety, pagination semantics, and return shape adequately for a one-parameter list tool. Only the lack of any guidance on report_id's origin or on error/empty cases keeps it below 5.

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% and the single parameter (report_id) is undocumented in both schema and description. The phrase 'of a report' weakly implies report_id identifies the target, providing minimal compensation but no format or sourcing detail.

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?

States a specific verb and resource ('List the pages of a report'), which is unambiguous against siblings like workbooks_list_report_page_elements or workbooks_list_workbook_pages. It does not explicitly contrast with those siblings, so it falls short of a 5.

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?

No when-to-use guidance, prerequisites, or named alternatives. The agent must infer from the tool name that this is the right call for enumerating a report's pages rather than elements, columns, or queries.

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