confluence_getStorageToFile

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

No annotations exist, so the description must fully disclose behavior. It states the tool downloads XML to a local file and returns version/title/path, but it does not mention whether the file will be overwritten, what permissions are needed, or any side effects. For a download tool, these are basic behavioral details that are missing.

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 extremely concise with three short sentences: first states the action, second lists return values, third provides usage guidance. No redundant words; every sentence earns its place.

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 no annotations and no output schema, the description provides core information (purpose, return values, one use case) but lacks details on error handling, file overwrite behavior, and prerequisites. For a simple download tool, it is minimally complete but could be more thorough.

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 clear descriptions for both parameters (contentId and filePath). The description adds no additional meaning beyond the schema, so the baseline of 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?

Clearly states the tool downloads Confluence page body.storage XML to a local file for surgical edits. The verb 'Download' and resource 'page body.storage XML' are specific, and the mention of 'surgical edits (large templates)' adds context. However, it does not explicitly differentiate from related read tools like confluence_getSpaceTemplateToFile, though the sibling list includes that tool.

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?

Provides implicit guidance: 'Prefer this over stuffing huge storage into chat' suggests when to use this tool (for large templates) but does not explicitly state when not to use or list alternatives. The sibling tools are named but not mentioned in the description, so an agent must infer context based on tool names.

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