list_resource_pools

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not mention permissions, pagination, or response characteristics beyond the output schema. It does add useful context about the downstream use of resource_pool_id.

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 two focused sentences with no filler. The first sentence states the action and scope, and the second provides the downstream purpose. Every sentence earns its place.

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 need no explanation. The two required parameters are clearly documented in the schema, and the description explains why the results matter downstream. Nothing essential is missing for an agent to call this tool correctly.

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 input schema already covers both parameters with helpful 'obtain from' guidance, so schema description coverage is 100%. The description adds downstream context about resource_pool_id but does not provide additional parameter-level semantics beyond what the schema already states.

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 states a specific verb ('List'), a specific resource ('resource pools'), and the scope ('on a host or cluster'). It clearly distinguishes this tool from the many sibling list_* tools by naming a unique resource type and giving a precise scoping condition.

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 explicitly explains when the output is needed: resource_pool_id is required by create_desktop_pool and create_rdsh_farm provisioning_settings. It does not explicitly state when not to use this tool, but no sibling tool lists resource pools, so the usage context is clear.

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