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 clearly describes the tool's behavior: how it finds sections based on heading levels (H1 vs H2/H3), what gets replaced ('replaces everything from that heading to the next section boundary'), and that the heading must be included in the markdown. This provides substantial behavioral context beyond basic parameters.

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 with three sentences that each add value: the core functionality, detailed behavioral rules for different heading levels, and comparative efficiency guidance. There is no wasted text, and key information is front-loaded.

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 does well by explaining the replacement behavior, heading-level rules, and efficiency comparison. However, it doesn't mention potential side effects, error conditions, or what happens if the heading isn't found, leaving some gaps in completeness.

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 all three parameters. The description adds some context about 'heading' being case-insensitive and that 'markdown' must include the heading, but these details are already covered in the schema descriptions. This meets the baseline for high schema coverage.

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 ('Update a section of a page by heading name'), the resource ('page'), and distinguishes it from sibling tools by explicitly mentioning 'More efficient than replace_content for editing one section of a large page.' This provides clear differentiation from the sibling 'replace_content' 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 explicit guidance on when to use this tool versus alternatives: 'More efficient than replace_content for editing one section of a large page.' This directly tells the agent when to prefer this tool over a sibling, fulfilling the highest criteria for usage guidelines.

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