notion_list_pages

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

The description discloses key behaviors: listing only cached pages (read-only, local), specific fields returned, and newest-first sorting. With no annotations, it sufficiently covers what the tool does, though it omits details like auth or if empty results occur.

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 sentence that front-loads the verb and resource, includes key details, and has no redundant information. 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?

For a simple list tool with no parameters and no output schema, the description is complete enough. It could briefly mention the output structure, but it's not essential.

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?

There are zero parameters, so the baseline is 4. The description adds no parameter information, which is fine as there are none to describe.

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 lists Notion pages, specifies the fields (titles, last edited, hierarchy), and sorting (newest first). It distinguishes itself from sibling tools like notion_search and notion_read_page by highlighting local caching.

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 describing the tool's purpose (listing cached pages), but there is no explicit guidance on when to use this versus alternatives like notion_search or notion_list_databases.

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