confluence_delete_attachment

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states 'Delete an attachment' without mentioning whether this soft-deletes (moves to trash) or permanently deletes by default, the effects on related content, or required permissions. The 'purge' parameter in the schema implies a trash mechanism, but the description does not clarify this.

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 very concise (4 words) with no wasted words, and the most critical information (verb + resource) is front-loaded. However, it lacks structural elements like bullet points or explicit parameter links.

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 the tool's simplicity (2 parameters, no output schema), the description is minimally adequate. However, it fails to explain the deletion lifecycle (e.g., trash vs permanent) or guide the agent on when to use 'purge', leaving gaps for a complete understanding.

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 coverage is 100% (both parameters have descriptions), so the baseline is 3. The description adds no additional meaning beyond what the schema already provides, such as explaining the relationship between 'purge' and the trash concept.

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 verb ('Delete') and resource ('attachment'), making the core action unambiguous. However, it does not differentiate this tool from sibling tools like 'confluence_delete_page' or 'confluence_delete_blog_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?

No guidance is provided on when to use this tool versus alternatives, such as when to use 'confluence_get_page_attachments' first or how 'purge' interacts with the deletion lifecycle. The agent has no context for appropriate usage.

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