list_sessions

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context by naming common filter fields and enumerating session states (CONNECTED, DISCONNECTED, PENDING), which helps interpret results. However, it does not mention pagination behavior, default limits, or whether 'active' excludes historical/ended sessions.

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 with the core purpose, followed by two concise, high-value lines about filters and states. Every sentence earns its place with no filler 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?

The tool has an output schema and fully documented parameters, so the description does not need to explain return values or parameter syntax. It covers the essential context: what is listed, which fields are useful for filtering, and which states may appear. The main gap is the absence of usage guidance versus sibling tools, but for a simple list operation the description is reasonably complete.

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%, so the baseline is 3. The description adds value beyond the schema by listing common filter fields (user_name, desktop_pool_id, machine_name, client_name, state) and enumerating session states, which supplements the filter parameter's schema description. This gives the agent practical guidance on constructing filters.

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's function: 'List active user sessions in the environment.' This distinguishes it from sibling tools like get_session, disconnect_sessions, and logoff_sessions. It is specific about the resource (user sessions) and action (list), though it does not explicitly contrast itself with any sibling.

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 no guidance on when to use this tool versus alternatives such as get_session for a single session or diagnose_session for deeper investigation. It provides filter fields and states, which are more about how to query than when to choose this tool. No exclusions or alternative recommendations are mentioned.

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