vsphere_get_vm_summary

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds minimal context ('summary property') without detailing what the summary includes or any side effects. Since annotations cover the safety profile, a moderate score is appropriate.

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 concise sentence that front-loads the action and resource. It avoids waste but omits necessary detail on parameters and usage context. Efficiency is good, but completeness sacrifices some structure.

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?

With an output schema present, return values are not required. However, the description fails to explain when to use this tool over similar ones (e.g., vsphere_get_vm) and does not describe the 'release' parameter or its default behavior. For correct invocation and selection, the description is insufficient.

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 must compensate. It explains 'vm' via example (vm-42) but does not clarify its format beyond that. The 'release' parameter is completely unmentioned, leaving its purpose and acceptable values ambiguous. The example only partially helps for one parameter.

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 action (Get), resource (VirtualMachine summary property), and mechanism (through VI/JSON by VM id) with an example. However, it does not explicitly differentiate from vsphere_get_vm, which may retrieve the full VM object, thus missing sibling differentiation.

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 explicit guidance on when to use this tool vs alternatives like vsphere_get_vm or vsphere_query_properties. The example implies a specific VM ID format but does not exclude use cases or mention prerequisites. Agents have no basis for choosing this tool over siblings.

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