confluence_getSpaceTemplateToFile

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

With no annotations, the description must fully disclose behavior. It mentions the 404 issue and identification methods but does not discuss file overwrite behavior, authentication needs, or rate limits. Adequate but not comprehensive.

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 defines the action, second adds usage constraints. No redundant words. Front-loaded with essential information.

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?

Covers main action, required parameters, identification, and a known issue. No output schema but output is a file. Missing details like whether file overwrites or appends. Nearly complete for a straightforward 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 has 100% coverage with descriptions. The description adds context that templateId and name can be used together and that name supports substring matching. Also clarifies filePath as absolute path. Adds value beyond schema.

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 verb 'download', resource 'space page template body.storage', and output 'local XML file'. Distinguishes from siblings by being the only template download to file tool. Also provides identification methods and a specific constraint (GET by id alone 404s on DC).

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 explains required spaceKey and identification via templateId/exact/partial name, and warns about a 404 issue. However, it does not explicitly compare with alternative tools like confluence_getStorageToFile or specify when to use this over others.

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