Retrieve a paginated list of all RDS (Remote Desktop Session Host) farms in the Horizon environment, with optional filters to narrow results.
List all RDS (Remote Desktop Session Host) farms in the environment.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-based) | |
| size | No | Results per page (max 1000) | |
| filter | No | Horizon filter JSON string |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are presentaint; no behavioral details beyond the word 'List' are disclosed. It does not mention pagination, result limits, or that it is read-only. The description simply restates the operation.
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?
Single sentence, front-loaded with the verb 'List' and resource. No redundancy or filler.
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?
A complete output schema exists, so return shape is covered. Still, with no annotations and no guidance on pagination/filtering behavior or when to use siblings, the description leaves an agent somewhat under-informed for a paginated list call.
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 coverage is 100%, so page, size, and filter are already documented. The description adds no meaning about how filters interact or how pagination behaves; baseline 3 applies because the schema does the work.
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?
Description clearly states the verb 'List', the resource 'RDS farms', and the scope ('all', 'in the environment'). It is distinguishable from sibling get_rdsh_farm (single farm) and create/update/delete/action variants.
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?
No guidance on when to use this tool vs alternatives such as get_rdsh_farm or how it relates to the pagination/filter parameters. The usage context must be inferred from the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.