Better Notion MCP

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds some context about what 'most tools' do automatically, but doesn't disclose important behavioral traits like conversion limitations, error handling, performance characteristics, or what happens with malformed content.

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 brief and to the point with two sentences. However, the second sentence about 'most tools handle markdown automatically' feels somewhat disconnected and doesn't clearly enhance understanding of this specific tool's purpose or usage.

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 conversion tool with no output schema, the description should explain what format the output takes (blocks structure vs markdown string) and any transformation characteristics. The annotations cover safety aspects, but the description lacks crucial information about the conversion behavior, limitations, and expected output format.

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 schema already documents both parameters thoroughly. The description mentions the two conversion directions but doesn't add meaningful semantic context beyond what the enum values already indicate. No format details, examples, or constraints beyond the schema.

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 converts between markdown and blocks formats with specific direction options. It distinguishes the tool's core function but doesn't explicitly differentiate from sibling tools like 'pages' or 'blocks' that 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 guidance - only mentioning that 'most tools handle markdown automatically' which vaguely suggests this might be for specialized cases. No explicit when-to-use vs when-not-to-use instructions, no mention of alternatives among sibling tools, and no prerequisites are provided.

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