pool_list

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

Adds the 'Paginated envelope' behavior and the verify-pair relationship beyond what readOnlyHint/idempotentHint annotations provide. Does not contradict annotations, though it omits details like error handling or empty-result behavior.

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 compact and front-loaded: a one-line summary, a usage note, and a minimal args list. There is no redundant material, making it easy to scan.

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?

Covers the returned fields, pagination envelope, and config target even without an output schema. The exact envelope structure (e.g., total count, next_page token) is left unspecified, but the description is still adequate for a simple list operation.

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?

With 0% schema description coverage, the description fully compensates by explaining each parameter: limit as page size, offset as page offset, and target as a Horizon config reference. This is sufficient for using the tool, though it doesn't add edge-case constraints.

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?

States 'List Horizon desktop pools' with specific fields and type enumerations (AUTOMATED/MANUAL/RDS), clearly distinguishing it from sibling tools like app_pool_list and farm_list. The '[READ]' prefix reinforces the read-only nature.

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?

Identifies the tool as 'verify pair for pool_set_enabled and pool_push_image', giving a concrete use case. Does not explicitly exclude alternatives like app_pool_list, but the sibling names and pool-type focus imply when this tool applies.

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