list_vm_disks

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action 'List all disks' without mentioning whether it is read-only, what happens if the VM does not exist, or how disks are returned. The 'Args' section adds no behavioral context.

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 front-loaded with the primary purpose. The 'Args' section repeats schema information but adds minimal value; however, the overall length is appropriate and free of fluff.

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?

Although an output schema exists, the description lacks usage context, behavioral transparency, and parameter clarity. For a single-parameter tool with no annotations, this is incomplete and leaves the agent guessing about edge cases and appropriate invocation.

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?

The schema provides vm_id with no description, and the description only adds 'The VM identifier', which is largely redundant with the parameter name. It does not specify whether the ID is a UUID, name, or how to obtain it, failing to compensate for the 0% schema description coverage.

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 'List all disks attached to a virtual machine' with a specific verb and resource. This distinguishes it from sibling tools like get_vm_adapters or get_vm_graphics, which list other types of VM information.

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 is provided on when to use this tool versus alternatives. The description does not mention any context, prerequisites, or exclusions, leaving the agent without information on how this tool fits among the many VM-related sibling tools.

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