add_attachment_from_confluence

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

No annotations are present, so the description carries full burden. It mentions authentication requirements but lacks details on side effects (e.g., does it modify Confluence?), error conditions, rate limits, or permissions required. This is insufficient for a cross-system operation.

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?

Single sentence efficiently conveys the action and authentication method. No unnecessary words; all information is relevant and front-loaded.

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?

The description covers the high-level process and auth but lacks details about result handling, failure scenarios, and the linking between Confluence attachment and Jira issue. Given no output schema and moderate complexity, it is minimally adequate but not complete.

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%, and the description adds no additional meaning to individual parameters beyond their schema descriptions. The verb 'Download and upload' frames the action but does not enhance parameter semantics. Baseline score 3 is appropriate.

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?

Description clearly states the tool downloads an attachment from Confluence and uploads it to a Jira issue, specifying the source and target. It distinguishes itself from sibling 'add_attachment_from_public_url' by mentioning Confluence authentication (PAT or SSO cookies).

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 implies usage for Confluence attachments but does not explicitly state when to use this tool versus 'add_attachment_from_public_url' or any prerequisites. No exclusion criteria or guidance on alternatives is provided.

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