download_iso

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

With no annotations provided, the description carries the full disclosure burden and does so well: it labels the operation DESTRUCTIVE, requires confirm=true to execute, describes the preview behavior, and discloses the SSH dependency. It does not address overwrite semantics or failure cleanup, but the critical safety behaviors are surfaced.

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 front-loaded with the DESTRUCTIVE label and purpose in the first sentence, then provides mechanism, prerequisite, and an Args block. Every sentence adds value with no fluff; the Args explanations justify their length given the 0% schema coverage.

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 having no annotations, the description covers the tool's purpose, SSH mechanism, prerequisite, downstream mount_iso integration, and complete parameter semantics. Since an output schema exists, return values are already covered, leaving no significant gaps.

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%, yet the description compensates fully by explaining every parameter: url (with example), destination (with default), filename (clarifying that the empty-string default means 'derived from URL'), and confirm (which gates execution and returns a preview otherwise). This goes well beyond the schema's bare defaults.

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 opens with 'DESTRUCTIVE: Download an ISO file from a URL to the NAS,' which is a specific verb+resource+destination statement. It is clearly distinguished from sibling tools like check_iso, mount_iso, and unmount_iso, which concern different lifecycle stages.

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?

The description provides clear usage context by explaining the ISO 'can then be mounted to a VM using mount_iso with path shared://ISO/<filename>' and by stating the SSH prerequisite. However, it does not explicitly state when-not-to-use or name alternative download mechanisms, so it stops short of a 5.

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