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. It discloses key behavioral traits: it is destructive ('Deletes existing blocks and writes new ones'), specifies the input format (markdown), and references syntax support from 'create_page'. However, it lacks details on permissions, error handling, or response format, which are important for a destructive 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 front-loaded with the core action ('Replace all page content with the provided markdown'), followed by essential behavioral details. Every sentence adds value: the first states the purpose, the second clarifies destructiveness, and the third provides syntax context. No wasted words.

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 a destructive tool with no annotations and no output schema, the description is moderately complete. It covers the purpose, behavior, and input context well, but lacks information on permissions, error cases, or what the tool returns (e.g., success confirmation or updated page details), which are important for safe usage.

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 ('page_id' and 'markdown'). The description adds some context by explaining that 'markdown' is 'replacement' content and references 'create_page' for syntax, but does not provide additional semantic details beyond what the schema offers (e.g., format examples or constraints).

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 ('Replace all page content'), the resource ('page'), and the mechanism ('with the provided markdown'). It explicitly distinguishes this from siblings like 'append_content', 'update_page', or 'create_page' by emphasizing it deletes existing content before writing new content.

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: when you want to completely overwrite page content with new markdown. It implies alternatives by referencing 'create_page' for syntax compatibility, but does not explicitly state when not to use it (e.g., vs. 'append_content' for adding or 'update_page' for partial updates).

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