download_file_restore

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

No annotations are provided, so the description must fully disclose behavioral traits. It only describes the parameters without mentioning whether the download is destructive, the nature of the response (e.g., binary stream), or required permissions.

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 short and includes an organized 'Args' list, making it easy to scan. It is front-loaded with the main action, and every sentence is informative, though minimal.

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 the absence of annotations and an output schema (which may cover return format), the description lacks details on the output type, size limits, or prerequisites. For a download tool, more contextual completeness is needed.

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 0%, so the description should compensate. It provides minimal explanation: 'The node name', 'Storage ID', 'Backup volume ID', and 'Path of the file to download from the backup'. This adds little beyond the parameter names, especially for node, storage, and volume.

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?

The description clearly states 'Download a file from a vzdump backup', which specifies the verb and resource. It distinguishes from sibling list tools like list_backup_file_restore, but does not explicitly differentiate from get_vzdump_extractconfig.

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?

No guidance on when to use this tool vs alternatives like list_backup_file_restore or get_vzdump_extractconfig. The description implies usage for downloading a file from a backup but lacks context on prerequisites or exclusions.

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