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 states the tool appends content and supports markdown syntax, but doesn't mention whether this requires specific permissions, if the operation is reversible, what happens on failure, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 efficiently structured in two sentences: the first states the core purpose, the second provides important context about markdown support. There's no wasted text, and the most critical information (what the tool does) comes first. It could be slightly more concise by integrating the markdown note into the first sentence.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address important contextual aspects like what the tool returns, error conditions, permission requirements, or how the append operation interacts with existing content. The markdown syntax reference is helpful but doesn't compensate for the missing behavioral 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%, so the schema already documents both parameters adequately. The description adds some context by mentioning the markdown syntax is the same as 'create_page', which helps understand the 'markdown' parameter format, but doesn't provide additional details about parameter constraints or usage beyond what the schema provides.

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 action ('Append markdown content') and target resource ('to an existing page'), making the purpose immediately understandable. It distinguishes from siblings like 'create_page' (new page) and 'replace_content' (overwrite), though it doesn't explicitly name these alternatives. The description avoids tautology by specifying the operation beyond just the tool name.

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 context by specifying 'to an existing page' and referencing 'create_page' syntax, suggesting this is for modifying existing pages rather than creating new ones. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'update_page' or 'replace_content', nor does it mention prerequisites like needing the page ID or permission requirements.

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