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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description's only added behavioral detail is that results are ACL-filtered, which is useful but thin; it says nothing about page size, exhaustion signals, or ordering.

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?

One sentence, front-loaded with the verb and resource, no filler or redundancy. Nothing could be trimmed without losing information.

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?

An output schema exists, so return values need not be described. However, for a cursor-paginated list tool the description omits the pagination lifecycle (initial call, termination condition) and any differentiation from the many other list-style siblings, leaving a real gap.

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% for both parameters, so the description must carry the meaning. 'Inside a folder' loosely maps to folderId and 'next ... page' hints that cursor is a continuation token, but the schema allows cursor to be null and the description never explains that null starts the first page — the single most important usage detail for a pagination cursor.

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 states a specific verb and resource: 'Read the next ACL-filtered page of sheets directly inside a folder.' That is clearly a paginated folder-scoped list operation, and 'ACL-filtered' adds real meaning. It does not, however, distinguish itself from nearby siblings such as sheets_list, sheets_list_archived, or sheets_get_folder.

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?

There is no explicit when-to-use guidance and no named alternative. The word 'next' weakly implies this is a continuation call, but the agent is never told what to call first or how this differs from sheets_list or sheets_get_folder.

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