Add a comment to a Notion page or block by providing the parent object and rich text. Use it to leave feedback, notes, or annotations directly in your workspace.
Create a comment on a page or block
| Name | Required | Description | Default |
|---|---|---|---|
| parent | Yes | Parent object (page or block) | |
| rich_text | Yes | Array of rich text objects for comment content |
Changes observed during successful MCP inspections.
v1.6.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, yet it discloses nothing about permissions required, whether commenting is supported on all page/block types, whether replies/threading are supported, or any rate limits. Only the mutation intent itself is conveyed.
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?
A single front-loaded sentence with no wasted words. It is efficient, though the extreme brevity leaves no room for the behavioral context a mutation tool needs.
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 write tool with no annotations, no output schema, and a nested parent object, the description should say more about permission requirements and the expected result. As written it is too thin to call correctly in ambiguous cases.
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 two parameters (parent, rich_text) are already documented. The phrase "on a page or block" loosely maps to the parent parameter but adds no format or structural detail beyond the schema, so the baseline of 3 applies.
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?
States a specific verb and resource ("Create a comment") plus the target scope ("page or block"). It is clear on its own but never distinguishes itself from the sibling notion_get_comments or explains what makes commenting different from other write operations.
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?
No when-to-use guidance, no prerequisites, and no mention of the related notion_get_comments tool for reading existing comments. Usage is only implied by the verb "Create".
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.