Easy Notion MCP

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 effectively describes key behaviors: it returns metadata and markdown content, recursively fetches nested blocks, and details output conventions (e.g., toggles as +++ blocks). It also hints at integration with 'replace_content' for updates. However, it lacks details on error handling, rate limits, or authentication needs, which are important for a read operation.

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 appropriately sized and front-loaded, starting with the core purpose and then adding details about output conventions and usage context. Every sentence adds value, with no wasted words, making it efficient and easy to understand.

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 complexity of a read operation with recursive fetching and no output schema, the description is mostly complete. It explains what the tool returns (metadata and markdown content) and output conventions, but it could benefit from mentioning the response structure or potential limitations (e.g., pagination for large pages). The lack of annotations means the description does a good job but has minor gaps.

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 schema description coverage is 100%, so the schema already documents all three parameters (page_id, include_metadata, max_blocks). The description does not add any parameter-specific details beyond what the schema provides, such as examples or edge cases. Thus, it meets the baseline for high schema coverage without compensating with extra insights.

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's purpose with specific verbs ('read', 'return') and resources ('page', 'metadata', 'markdown content'), distinguishing it from siblings like 'list_pages' (which lists pages) or 'update_page' (which modifies pages). It explicitly mentions recursive fetching of nested blocks, which is a unique feature not implied by the name alone.

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 clear context for when to use this tool by mentioning 'read a page, modify the markdown, replace_content to update', implying it's for retrieving content before editing. However, it does not explicitly state when not to use it or name alternatives (e.g., 'list_pages' for summaries), so it falls short of a perfect score.

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