Get Parallels VM status

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the useful detail that the status returned is 'bounded', but it does not clarify what that bound is or describe any other behavioral nuances such as missing-VM handling.

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 a single sentence with no filler, and the main purpose is front-loaded. It conveys the key scoping constraint ('VM name or UUID') without wasting words.

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 one-parameter read-only tool with an output schema and read-only/idempotent annotations, the description is largely sufficient to invoke the tool correctly. The main gap is that 'bounded' is vague and there is no guidance on failure or not-found behavior, but the output schema can reasonably cover return details.

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 coverage is 0%, so the description carries the burden of explaining the single 'vm' parameter. It does this meaningfully by stating that the value can be a VM name or UUID, which is essential information an agent would not get from the bare schema title 'Vm'.

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 uses a clear verb ('Return') and resource ('status details'), and specifies that the target is identified by VM name or UUID. This distinguishes it from vm_list and other sibling tools at a basic level, though it does not explicitly contrast with siblings and the word 'bounded' is somewhat ambiguous.

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 intended use is implied: call this when you have a VM name or UUID and need status details. However, the description gives no explicit guidance about when not to use it or which sibling tool to prefer for related needs like waiting for readiness or listing all VMs.

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