create-comment

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

No annotations provided; the description states it creates comments (write operation) and returns the created comment ID, but does not disclose permissions, rate limits, or side effects beyond the basic mutation.

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?

Three sentences, no fluff, front-loaded with purpose, and efficiently structured to convey core functionality and usage variant.

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 no output schema, the description states the return value; it covers key usage variants (new comment vs reply) and rich text support; though missing error or permission details, it is reasonably complete for a straightforward creation tool.

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 coverage is 100% with parameter descriptions; the description adds context about discussion_id for replying and rich text support, but does not significantly extend 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 adds a comment to a Notion page, distinguishes between new discussion and reply, and is differentiated from the simpler sibling create-comment-simple.

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 explains when to use this tool (to add a comment) and hints at when to use discussion_id for replies, but does not explicitly list alternatives or when-not-to-use contexts beyond immediate scenarios.

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