Notion Workflow MCP

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

With no annotations provided, the description carries full burden. It discloses the append behavior (adds to end, doesn't replace) and mentions the return format ('更新后的任务元信息（不含完整 body）' - updated task metadata without full body). However, it doesn't cover permissions needed, error conditions, or whether the operation is idempotent/reversible, leaving gaps for a mutation tool.

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: first sentence states purpose and behavior, followed by clear Arg/Returns sections. Every sentence adds value—no fluff. It's front-loaded with the core action and uses bullet-like formatting for parameters and returns, making it easy to scan.

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 2-parameter mutation tool with no annotations but an output schema (which handles return values), the description is reasonably complete. It covers purpose, parameters, and return scope, though could improve by mentioning auth needs or error cases. The output schema existence reduces the burden, but some behavioral context (e.g., idempotency) is still missing.

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 clearly explains both parameters: task_id ('任务的 Notion 页面 ID' - Notion page ID of the task) and content ('要追加的文本内容' - text content to append). This adds essential meaning beyond the bare schema types (string, string), though it doesn't specify format constraints (e.g., ID structure, content length).

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 ('向已有任务追加内容' - append content to existing task) and resource ('任务' - task), distinguishing it from siblings like create_task (creates new) or update_task (general update). It specifies the exact location ('追加到页面 body 末尾' - append to end of page body), making the purpose unambiguous.

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 for appending to existing tasks, but doesn't explicitly state when to use this vs alternatives like update_task (which might replace content) or create_task (for new tasks). It mentions the task must already exist ('已有任务'), providing some context, but lacks explicit guidance on prerequisites or comparison with sibling tools.

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