session_list

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds a detailed response envelope, item fields, pagination semantics, substring matching for user, exact matching for pool, state value restrictions, and target configuration behavior. No contradiction with annotations.

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 front-loaded with a one-line summary, followed by a compact return-format paragraph and a structured Args list. Every section adds necessary information for a 6-parameter tool with no output schema; there is no fluff or redundancy.

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 list tool with 6 optional parameters and no output schema, the description exhaustively covers the response envelope, item fields, filtering behavior, pagination, and usage context. Missing details like error/rate-limit handling are non-essential for this read-only listing 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?

Schema description coverage is 0%, but the description fully compensates by explaining each parameter: user is a substring match, pool is an exact desktop-pool/farm id, state lists valid values, limit/offset are pagination controls, and target references config.yaml with default fallback behavior.

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 Horizon VDI sessions, filtered by user / pool id / state. Paginated.', which clearly identifies the verb, resource, and filtering scope. It also positions the tool as 'the verify pair for logoff/disconnect', differentiating it from sibling session mutation tools.

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?

It explicitly says to use this tool to 'get a session id or confirm a user's sessions here first' before logoff/disconnect. This provides clear context, but it does not explicitly mention when not to use it or name alternatives like session_get.

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