Delete Attachment

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

Description expands on the destructiveHint annotation by emphasizing irreversibility and deletion of all versions. Adds critical context beyond annotations, with no contradiction.

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?

Well-structured with sections and front-loaded warning, but slightly verbose for a simple operation. Still clear and 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?

Covers all critical aspects: action, consequences, best practices, parameter source, and return value. Fully adequate for a deletion tool with good annotations and schema.

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 has 100% coverage with detailed parameter description including example and warning. Description adds value by referencing get_attachments tool for finding attachment IDs.

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 'Permanently delete an attachment from Confluence' with specific verb and resource. It distinguishes itself from sibling tools like download or get 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?

Provides explicit when-to-use scenarios (remove outdated, clean duplicates, delete sensitive info) and best practices (verify ID, backup, check with owners). Could be improved by stating when not to use, but is still clear.

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