list_desktop_pools

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

No annotations are provided, so the description carries the full behavioral burden. It only says 'List' and does not explicitly state that the operation is read-only, nor does it clarify pagination behavior. The use of 'all' conflicts somewhat with the page/size parameters, which may mislead an agent into expecting a single uncapped response.

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 sentence with no filler, and the key information is front-loaded. It communicates the tool's purpose in the most compact useful form possible.

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 list endpoint, the parameter schema and output schema cover most invocation needs. The main gap is that the description does not reconcile 'all' with the paginated page/size defaults, and it could explicitly note the read-only nature, but overall it remains sufficiently complete for a straightforward list tool.

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 100%, with page, size, and filter all documented meaningfully. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 names a specific verb ('List'), a specific resource ('desktop pools'), and a scope ('VDI and RDS' in the Horizon environment). It clearly conveys a collection endpoint and is readily separable from sibling tools like get_desktop_pool, create_desktop_pool, and list_rdsh_farms by verb and resource.

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?

Usage is implied: this tool is for enumerating desktop pools. However, the description provides no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as get_desktop_pool for a single pool or list_rdsh_farms for farms.

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