listNotionPages

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

There are no annotations, so the description carries the full burden. It discloses that this is a read operation ('Retrieves') and restricts scope to pages the user has access to, but it does not disclose output format, pagination, sorting, or whether it includes archived pages or page content. This leaves some behavioral aspects unknown.

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, front-loaded with the action 'Retrieves' followed by the resource. Every word contributes, with no extraneous detail.

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 no output schema and no annotations, the description must explain what the list returns, but it only says 'a list of pages.' It does not clarify whether the response contains page IDs, titles, metadata, or full content, which is a notable gap for a tool with no structured output definition. Given the low complexity, some additional detail about return format would be needed for full completeness.

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 has no parameters, and schema coverage is 100% (empty schema). The description adds no parameter-specific information, which is appropriate since none exist; the baseline for zero parameters is 4.

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 the specific verb 'Retrieves' with the resource 'a list of pages the user has access to in Notion,' which clearly states the tool's function. It distinguishes from sibling tools like listNotionDatabases (different resource) and searchNotion (search vs. list) by specifying it directly lists pages.

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?

The description provides no explicit guidance on when to use this tool versus alternatives like searchNotion or readNotionPage. The intended use is implied by the phrasing 'pages the user has access to,' but no exclusions or alternative tool references are given.

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