pve_storage_download

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

With no annotations, description discloses mutation action, dry-run default, confirm requirement, async nature, and UPID return. Provides good transparency for a tool with no 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?

Single sentence packed with essential information: mutation, download action, content types, dry-run/confirm, async return. No wasted words, front-loaded.

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 output schema existing, description does not explain key parameters (node, checksum, etc.) that have no schema descriptions. Incomplete for a tool with 9 parameters and low schema coverage.

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 description coverage is only 11%, and the description adds no details for most parameters (e.g., node, checksum, checksum_algorithm, proximo_target). Only content and confirm are indirectly explained.

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 an ISO or CT template from a URL into storage, specifying content types. It distinguishes from sibling storage tools by focusing on download action.

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?

Mentions dry-run and confirm flag, but lacks explicit guidance on when to use this tool versus alternatives like pve_storage_content or pve_storage_content_delete.

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