Better Notion MCP

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

The description adds some behavioral context beyond annotations: it mentions the parent_id requirement for create operations and that get returns markdown content. However, with annotations covering basic safety (readOnlyHint=false, destructiveHint=false), the description doesn't elaborate on important behaviors like rate limits, authentication needs, or what specific actions might be destructive (like archive).

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 concise with two sentences that cover the main operations and key constraints. The first sentence lists all actions efficiently, and the second provides two important usage notes. There's no wasted language, though it could be slightly more structured with clearer separation between action types.

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 complex tool with 13 parameters, multiple actions, and no output schema, the description is somewhat incomplete. It covers basic operations and two specific constraints, but doesn't provide enough context about action differences, error conditions, or what to expect from non-get operations. Given the tool's complexity, more guidance would be helpful.

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?

With 100% schema description coverage, the input schema already documents all 13 parameters thoroughly. The description adds minimal parameter semantics - only mentioning parent_id for create actions and that get returns markdown content. It doesn't explain parameter relationships or action-specific requirements 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 tool handles page lifecycle operations (create, get, update, etc.) and returns markdown content for get operations. It specifies the verb ('Page lifecycle: create, get, update...') and resource ('pages'), but doesn't explicitly differentiate from sibling tools like 'blocks' or 'databases' which might handle similar 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 minimal usage guidance - only mentioning 'Requires parent_id for create' and 'Returns markdown content for get'. It doesn't explain when to use this tool versus alternatives like 'blocks' for content manipulation or 'databases' for structured data, nor does it provide context about prerequisites or exclusions for different actions.

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