notion_retrieve_page

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Retrieve' implies a read-only operation, but the description doesn't clarify authentication requirements, rate limits, error conditions, or what the response contains (e.g., page content, metadata). The format parameter description hints at behavioral differences between JSON and markdown outputs, but this is insufficient for a tool with no annotation coverage.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose ('Retrieve a page from Notion'), making it immediately understandable without unnecessary elaboration.

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 the lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'page' entails in Notion's context, what data is returned, or how this differs from other retrieval tools. For a tool with no structured behavioral hints, the description should provide more context about the operation's scope and results.

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%, so the schema fully documents both parameters (page_id format, format enum with defaults and usage guidance). The description adds no additional parameter semantics beyond what's already in the schema, meeting the baseline score of 3 when the schema does the heavy lifting.

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 verb ('retrieve') and resource ('a page from Notion'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'notion_retrieve_block' or 'notion_retrieve_database', which also retrieve specific Notion resources, leaving some ambiguity about when to use this specific retrieval tool.

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. With multiple sibling retrieval tools (e.g., notion_retrieve_block, notion_retrieve_database, notion_retrieve_user), there's no indication of what makes a 'page' distinct or when this tool is preferred over others for retrieval operations.

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