confluence_comment_delete

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

No annotations provided, so description transparently states irreversibility, destructive guard (confirm: true), return format (YAML), and prevents accidental API calls. Lacks rate limit or auth details.

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, front-loaded with the action, no fluff. Every sentence adds critical information: action, constraints, behavior, return format, and CLI mirror.

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 simple deletion tool with 3 parameters, no output schema, and no annotations, the description covers purpose, usage constraints, behavioral implications, and return type completely.

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 covers 100% of parameters; description adds value by linking comment_id to the list tool and emphasizing the confirm parameter as a destructive guard, providing context 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 deletes a Confluence comment, specifies the required comment_id from the list tool, and distinguishes between footer and inline kinds, differentiating it from sibling tools.

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 context on when to use (after listing comments) and constraints (kind values, confirm guard), but does not explicitly contrast with alternatives like editing or resolving comments.

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