session_list

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

Beyond the readOnly/idempotent annotations, the description discloses the pagination envelope, item fields, filter semantics (substring vs exact match), and state enum values, which are valuable behavioral details not present in the structured metadata.

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 well-structured with a brief summary, return envelope information, and an args list. No redundant text; each clause adds value, and the front-loading of purpose is effective.

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?

Despite having no output schema and sparse input schema, the description provides everything needed: return format, item attributes, parameter behavior, and integration with sibling tools. It is complete for the tool's complexity.

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 zero schema descriptions, the description fully compensates by explaining each argument: substring match for user, exact pool id, allowed state values, default limit of 50, offset, and target source. This is critical for correct invocation.

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 clearly states the tool lists Horizon VDI sessions with filtering by user, pool, and state, and mentions pagination. It distinguishes itself from siblings by explicitly naming it as the verify pair for logoff/disconnect operations.

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 gives explicit usage context: 'This is the verify pair for logoff/disconnect — get a session id or confirm a user's sessions here first.' This tells the agent when to use this tool versus session_logoff or session_disconnect.

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