systemprompt_list_notion_pages

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits such as sorting order and metadata returned, but lacks details on permissions required, pagination behavior, rate limits, or error handling. The description does not contradict any annotations, but for a tool with no annotations, it provides only moderate transparency.

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 front-loaded with the core purpose in the first sentence and adds essential details in the second, with no wasted words. It efficiently conveys the tool's functionality, sorting, and output in two concise sentences, making it easy to parse and understand quickly.

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?

Given no annotations and no output schema, the description provides basic completeness by stating the action, sorting, and metadata returned. However, it lacks details on authentication needs, response format beyond metadata names, or limitations, which are important for a list operation with potential access controls. It is adequate but has clear gaps in context.

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?

Schema description coverage is 100%, with the single parameter 'maxResults' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as default behavior or constraints. With high schema coverage, the baseline score of 3 is appropriate as the description does not compensate but also does not detract.

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 specific action ('Lists all accessible Notion pages'), resource ('Notion pages'), and scope ('in your workspace'), with explicit sorting ('sorted by last edited time') and output details ('Returns key metadata including title, URL, and last edited timestamp'). It distinguishes from siblings like 'systemprompt_search_notion_pages' by emphasizing comprehensive listing without search filters.

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 implies usage for retrieving all pages in a workspace, sorted by recency, which provides clear context. However, it does not explicitly state when to use this tool versus alternatives like 'systemprompt_search_notion_pages' or 'systemprompt_list_notion_databases', nor does it mention exclusions or prerequisites, leaving some ambiguity in sibling differentiation.

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