list_vms

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

Lacking annotations, the description carries full burden. It states the tool returns state, CPU, and RAM but does not disclose whether it lists all VMs globally or per user, if it includes stopped VMs, or any side effects. For a read-only list operation, this is adequate but not rich.

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?

Single sentence with no wasted words. Information is front-loaded: the action and resource are immediately clear.

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 existence of an output schema (not provided), the description complements it by listing key fields. However, it omits potential context like pagination, ordering, or scope (e.g., all VMs vs. user's VMs). Still, for a 0-parameter list tool it is fairly complete.

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?

No parameters exist, so schema description coverage is 100% trivially. Description adds no param details since none are needed. Baseline of 4 for zero-parameter tools is appropriate.

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?

Description clearly states it lists all virtual machines and specifies the returned fields (state, CPU, RAM). The verb 'list' and resource 'virtual machines' are unambiguous, and it distinguishes this tool from siblings that list other resources.

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. While siblings include many listing tools (e.g., list_datasets, list_alerts), the description does not provide context for when to choose list_vms over others, nor does it mention any prerequisites or filters.

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