vsphere_list_clusters

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context beyond this: it explains that the result includes capacity, DRS, and HA configuration, and details filtering behavior (case-insensitive substring, glob matching, datacenter filter, paging). No contradictions with annotations.

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 concise and well-structured: a one-sentence summary followed by a clear Args list. Every sentence is informative, with no fluff or repetition of schema information.

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 tool's moderate complexity (read-only list with filters) and the availability of an output schema, the description adequately covers purpose, parameters, and result content. It does not mention edge cases like default limits or sorting, but these are likely covered by the output schema or are not critical for correct invocation.

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 the description fully compensates. Each parameter is given meaningful semantics: name with substring/glob matching, datacenter filtering, limit for max results, and offset for paging. This adds substantial value beyond the bare schema.

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 'List compute clusters with their capacity, DRS and HA configuration' uses a specific verb and resource, clearly distinguishes from sibling tools like vsphere_list_hosts and vsphere_list_vms, and specifies the scope (compute clusters).

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 makes it obvious this tool is for listing cluster information, with no exclusions or alternatives mentioned. It lacks explicit 'when not to use' guidance, but the context is clear enough for an agent to choose it appropriately among siblings.

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