Download All Content Attachments

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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly focuses on value-add: the payload shape (base64 embedded resources), the reason it exists (no server filesystem access over MCP), and the 50 MB per-file cap with an error entry surfaced in the summary. That size-limit and failure-handling behavior is exactly the kind of trait the agent could not infer from the annotations.

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?

Front-loaded with the action and resource in the first sentence, followed by the return-format rationale and the size-limit caveat. No filler, though the second sentence's 'available over the MCP protocol' explanation is slightly verbose relative to its informational value.

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?

With one simple parameter, no output schema, and full annotation coverage, the remaining burden is small and largely handled: the agent knows the return is a set of base64 resources plus a summary containing per-file errors. Only the exact summary/response structure is left unspecified, a minor gap for a download-all tool.

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?

There is a single parameter with 100% schema description coverage, which already documents the content ID and gives an example. The description adds no further parameter meaning (e.g., content_id accepts blog posts as well as pages is only in the schema), so the baseline of 3 applies.

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?

States a concrete verb and resource: downloads ALL attachments for a Confluence content item, returned as embedded base64 resources. The word 'all' plus 'content item' distinguishes it from the single-attachment sibling confluence_download_attachment and the metadata-only confluence_get_attachments, though it never names those siblings 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?

Usage is only implied: 'all attachments ... as embedded resources' hints at when this beats confluence_get_attachments (listing) or confluence_download_attachment (one file), but the description never states the selection criteria or prerequisites. The agent must infer the boundary from the sibling names alone.

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