get_vm_cdroms

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

No annotations are present, so the description must convey behavioral details. It only states the read action but does not disclose whether the operation is read-only, how errors are handled, or any prerequisites (e.g., VM state). No additional context about side effects or return behavior is provided.

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 very short and front-loaded, with no fluff. The 'Args' block is somewhat redundant with the schema but does add a brief explanation. Overall, it is efficient, though it omits important contextual details.

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?

For a simple getter with one parameter and an output schema, the description is mostly adequate but lacks usage guidance and behavioral transparency. The presence of an output schema covers return values, but the absence of annotations and any when-to-use notes makes it incomplete for a tool in a large sibling set.

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 description adds 'vm_id: The VM identifier', which offers a basic human-readable explanation beyond the schema's title 'Vm Id'. Since schema description coverage is 0%, this is the only parameter documentation, but it remains vague and does not specify how to obtain the ID or constraints on its format.

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 the tool's function: 'Get CD-ROM drives and mounted ISOs for a virtual machine.' It uses a specific verb ('Get') and a specific resource ('CD-ROM drives and mounted ISOs'), and it is distinct from sibling tools like get_vm_disks or get_vm_adapters.

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 no guidance on when to use this tool compared to alternatives. There is no mention of scenarios where this tool is preferred, nor any exclusions or references to sibling tools such as list_vm_disks or get_vm_states.

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