delete_comment

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

Discloses destructive nature ('DESTRUCTIVE WRITE', 'Cannot be undone'), ownership requirements, and dry_run safety mechanism. No annotations exist, so description carries full burden and meets it.

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?

Two efficient sentences front-loaded with 'DESTRUCTIVE WRITE.' No wasted words; every clause adds value.

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 annotations, no output schema, and 4 parameters, the description covers purpose, constraints, parameter behavior, and side effects. A minimal but complete guide for correct invocation.

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?

Adds meaning for all four parameters: comment_id (implied required), kind (explains values post vs note and implication on pub), pub (needed for post comments), dry_run (default true, must set false to execute). Schema has 0% description coverage; description compensates fully.

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 deletes a comment (verb+resource) with ownership constraints, distinguishing it from siblings like react_to_comment or comment_on_post.

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?

Explicitly states when to use (own comments or owner's publication), warns about irreversibility, and explains how to override dry_run default.

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