Notion Workflow MCP

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

No annotations are provided, so the description carries the full burden. It discloses that the tool retrieves details and can optionally include body content, which is useful behavioral context. However, it doesn't mention permissions, rate limits, error conditions, or whether it's a read-only operation (though 'get' implies read-only). The description adds some value but lacks comprehensive behavioral details.

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 well-structured and concise. The first sentence states the purpose clearly, followed by organized sections for Args and Returns. Every sentence adds value: the purpose, parameter explanations, and return behavior. No wasted words or redundancy.

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 the tool's low complexity (2 parameters, no nested objects) and the presence of an output schema (which handles return values), the description is reasonably complete. It covers purpose, parameters, and return conditions. However, for a tool with no annotations, it could benefit from more behavioral context like error handling or permissions.

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 0%, so the description must compensate. It provides clear semantics for both parameters: note_id as a Notion page ID and include_content as a boolean controlling body content inclusion, with a default value. This adds meaningful context beyond the bare schema. However, it doesn't specify the format of note_id (e.g., UUID) or detail what 'body 内容' entails.

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's purpose: '获取单篇笔记的完整详情（含 body 内容）' (Get the complete details of a single note, including body content). It specifies the verb ('获取' - get) and resource ('笔记' - note), and distinguishes it from sibling tools like list_notes or search_notes by focusing on a single note. However, it doesn't explicitly differentiate from get_task or other get_* tools beyond the resource type.

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 it's for retrieving a single note's details, suggesting it should be used when you have a specific note_id. However, it lacks explicit guidance on when to use this versus alternatives like list_notes (for multiple notes) or search_notes (for filtered searches). No exclusions or prerequisites are mentioned.

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