Download Confluence Attachment

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

The description gives no behavioral details beyond the basic action. It does not disclose whether content is returned to the LLM, how save_path affects behavior, or if there are side effects, which is notable given openWorldHint is true and readOnlyHint is false.

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 a single sentence but it largely restates the tool name and title. It is under-specified rather than appropriately concise, offering little value beyond the structured metadata.

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?

Despite having an output schema and good parameter descriptions, the tool description lacks prerequisite context, usage scenarios, and behavioral expectations. For a download tool, this minimal description is insufficient for an agent to know when and how to invoke it correctly.

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%, with both parameters well-described: save_path explains save vs. return behavior, and attachment_id provides a concrete example. The description itself adds no parameter semantics, but the schema compensates fully.

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 'Download attachment content' uses a specific verb and resource, clearly indicating the tool's function. It distinguishes itself from siblings like get_content_by_id, which retrieves content rather than downloading attachments, though it omits the Confluence context explicitly.

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 about when to use this tool versus alternatives such as get_content_by_id or get_comments. The description is a bare statement with no context on prerequisites, exclusions, or appropriate use cases.

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