list_pages

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

There is no mention of pagination behavior, ordering, or what fields are returned, leaving the semantics of 'all pages' ambiguous given the page and per_page parameters. With no annotations, the description carries the full transparency burden and doesn't disclose result structure, authentication, or side effects.

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 a single sentence that is front-loaded with the action and resource, with no redundant details. Every word 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?

The tool lacks an output schema and annotations, and the description fails to clarify whether 'all pages' means all pages in the system or a page of results per the pagination arguments. It also doesn't indicate the response structure, leaving the context incomplete for an agent to fully understand the tool's behavior.

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 schema already documents both parameters (page and per_page) with clear descriptions, providing 100% coverage. The description adds no extra meaning about how to use the parameters, so it does not enhance parameter semantics 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 uses a specific verb 'List' with a clear resource 'pages' and clarifies the page type as Notion-like documents. This distinguishes it from sibling tools like get_page (single page) or list_files (files).

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 guidance is provided on when to use this tool over alternatives like get_page or get_page_tree, nor any exclusions or preconditions. The description only states the action without contextual usage cues.

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