confluence_download

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

No annotations are provided, so the description carries full burden. It discloses recursive download, YAML manifest return, directory creation (with tempdir fallback), and mirrors CLI behavior. It does not cover error handling or overwrite policy, but the core behaviors are transparent.

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?

Two sentences: first states action, second clarifies required parameters and return. No wasted words; information is front-loaded. The description is concise and well-structured.

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 7 parameters and no output schema, the description explains the overall behavior, the two input modes, and the return type (YAML manifest). It could mention whether the directory structure reflects the page hierarchy, but it is largely complete for a download 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?

Schema coverage is 100%, so baseline is 3. Description adds context by reiterating the id/space distinction and the default tempdir for output_dir, but the schema descriptions already cover each parameter adequately.

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 it downloads a Confluence page or space recursively into a directory. It distinguishes itself from sibling tools like confluence_read which likely reads content without downloading, and from confluence_delete which removes pages.

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?

Description specifies that either 'id' or 'space' must be provided, giving clear guidance on the two modes. It also mentions that it mirrors a CLI command. However, it does not explicitly compare to alternative tools for similar tasks (e.g., confluence_read).

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