vsphere_list_resource_pools

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

Annotations already declare readOnlyHint and idempotentHint, covering the safety profile. The description adds behavioral context by specifying the returned data (reservations, limits, current usage) and the paging behavior via limit/offset, which goes beyond the annotations without contradicting them.

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 extremely concise: one clear sentence stating the purpose, followed by a compact list of parameters. Every line earns its place with no redundancy, making it easy for an agent to parse quickly.

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 simple read-only list tool with three optional parameters and an output schema, the description covers the core behavior, filtering, and paging. It does not need to elaborate on return values since an output schema exists, and the low complexity means no further context is necessary.

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?

The JSON schema provides only types and defaults with no property descriptions, so the description's Args section adds essential meaning for all three parameters (name, limit, offset). This fully compensates for the 0% schema coverage, clearly explaining each parameter's role.

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 opens with 'List resource pools with their reservations, limits and current usage,' which clearly identifies the verb (list), the resource (resource pools), and the specific fields returned. This distinguishes it from sibling tools like vsphere_list_vms or vsphere_list_hosts, making the purpose unambiguous.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions. However, the context of sibling tools and the straightforward list nature imply its usage, which is acceptable for a simple read-only operation.

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