listNotionPages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add a key constraint: it only returns pages the user has access to, which is important context. However, it does not mention other behavioral aspects such as pagination, rate limits, or whether the response includes metadata. While the read-only nature is implied by 'Retrieves', there is no explicit safety disclosure.

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 concise sentence that immediately conveys the action and resource. It avoids unnecessary words and is well-structured for quick comprehension. Every word adds value.

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 tool with no parameters and no output schema, the description is minimally viable. It explains the primary function and a key behavioral filter (access). However, it lacks differentiation from sibling tools and does not provide context on when to use this tool over others, leaving the agent to infer the appropriate use case.

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 input schema has zero parameters, so the description does not need to explain parameter meanings. The baseline for zero parameters is 4, and the description does not introduce any conflicting information. It effectively communicates the tool's scope without parameter details.

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 the tool retrieves a list of pages in Notion, using the specific verb 'Retrieves' and the resource 'pages'. It also includes the scope 'user has access to', which is useful. However, it does not distinguish itself from sibling tools like 'searchNotion' or 'listNotionDatabases', which might also be used to find pages, so it falls short of a perfect score.

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 guidance on when to use this tool versus alternatives. There is no mention of exclusions or when a different tool like 'searchNotion' would be more appropriate. The only hint is the implied use case of listing accessible pages, but this is not explicitly stated as the recommended scenario.

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