pages_list

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

With no annotations, the description carries the disclosure burden. 'Returns' implies a read-only, side-effect-free operation, and the description usefully states the returned fields (titles, indices, dimensions, active status). However, it says nothing about ordering, pagination, or performance/rate characteristics.

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?

A single front-loaded sentence with no filler; the enumerated return fields are the only elaboration and each 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 no-param, no-annotation tool with no output schema, the description compensates reasonably by naming the return fields. It falls short of fully specifying the return structure (e.g., format of dimensions, ordering of the list), so it is strong but not exhaustive.

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?

The tool takes zero parameters, so the schema has no semantics to explain; per the baseline rule for 0-param tools, this dimension starts at 4. There is nothing parameter-related for the description to add.

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 gives a specific verb ('Returns') and resource ('the full list of pages in the current multi-page document'), then enumerates exactly what each entry contains. This clearly distinguishes it from the mutating siblings (pages_add, pages_switch, pages_duplicate, pages_delete).

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?

Usage is implied by the nature of the operation—enumerate pages before switching, duplicating, or deleting one—but the description never states when to call it or names alternatives. It provides context but no explicit routing guidance.

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