notes_delete_comment

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

The description discloses that deletion is permanent and cannot be undone, which is critical behavioral information. However, with no annotations provided, it lacks details on authentication requirements, rate limits, side effects on the note, or the response format (e.g., success/failure status).

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 with a clear main statement, bullet-pointed workflow tips, and a common use cases section with an example. Every sentence serves a purpose, and the most important information is front-loaded. No unnecessary words.

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?

The description covers the main purpose, prerequisites, and irreversibility. However, since there is no output schema, it should also explain the return value or success indication after deletion. This omission makes it slightly incomplete for an agent that expects to understand the full response.

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 coverage, the baseline is 3, but the description adds value by clarifying that comment_id is a UUID (not a number), providing an example JSON, and stating both parameters are required. This enhances understanding beyond the schema descriptions.

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 'Delete a comment from a note' and 'Permanently removes a comment from a note,' specifying the verb (delete) and resource (comment on a note). It distinguishes from sibling tools like notes_add_comment, notes_update_comment, and notes_list_comments by focusing on deletion.

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 workflow tips including that both note id and comment_id are required, comment_id is a UUID, and to use notes_list_comments to find the comment_id. While it doesn't explicitly state when not to use the tool, the tips and common use cases offer clear guidance on when to invoke it.

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