vsphere_query_properties

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, so the description's 'Read' is consistent but adds little. It mentions 'allowlisted' as a constraint, which is useful, but no further info on behavior (e.g., error handling, rate limits). With good annotations, the description adds marginal value.

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 front-loaded purpose and parameter list. No wasted words, but could be more structured. Appropriate length given simplicity.

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?

Output schema exists but description doesn't explain return format. 'Allowlisted' is vague—agent may not know which properties are allowed. No mention of error cases or how to handle missing properties. Adequate for a read-only tool with annotations, but incomplete for full agent autonomy.

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 description coverage is 0%, so description must compensate. It merely lists parameter names (mo_type, mo_id, property_path, release) without defining them or providing valid values. No explanation of what each parameter means or how they are used, e.g., mo_type as managed object type. Insufficient for an agent to correctly set parameters.

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 'Read one allowlisted VI/JSON managed-object property', defining verb (read), resource (property), and constraint (allowlisted). It distinguishes from sibling tools like vsphere_get_vm (which retrieves full VM) and list tools by specifying a single property query.

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. The description implies usage for reading a single property, but does not state when not to use it (e.g., if multiple properties needed, use vsphere_get_vm). Lacks exclusions or preferences.

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