confluence_delete_attachment

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

It discloses the destructive nature ('permanently removes the attachment') and explains the preview mode with confirmation step. Since no annotations are provided, this description carries the full burden and covers key behavioral aspects.

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 warning and argument list. Could be slightly more concise (e.g., 'permanently removes' vs. 'permanently removes the attachment'), but overall efficient.

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?

All parameters are explained, and the deletion workflow is described. However, it does not specify what the preview returns or the response on success/failure. Given no output schema, this gap reduces completeness.

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?

The Args section adds essential meaning beyond the schema: page_id accepts numeric IDs or URLs, attachment_title is a filename, confirm defaults to False. This compensates for 0% schema coverage.

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 an attachment from a Confluence page.' It specifies the resource (attachment) and the action (delete), distinguishing it from sibling tools like upload or list attachments.

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 explicitly instructs to show a preview to the user and obtain approval before deleting. It mentions the default preview mode. However, it does not contrast with alternative tools (e.g., when to use upload vs. delete).

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