list_sessions

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

With no annotations, the description carries the full burden. It discloses the non-obvious behavior that dead sessions are listed and still have output available, which is valuable. It also implicitly signals a read-only operation by not mentioning any side effects.

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?

Two sentences with no wasted words. The core purpose is in the first sentence, and the second provides essential context about dead sessions. Each sentence earns its place.

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 parameterless list tool with an output schema, the description adequately covers the main functionality and the critical nuance about dead sessions. It also references sibling tools for follow-up actions, making it self-contained within the toolset.

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?

The input schema has zero parameters, so there is nothing to document. The baseline is 4 for no-parameter tools, and the description appropriately avoids discussing parameters.

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 uses a specific verb and resource: 'List all SSH sessions.' It explicitly differentiates from siblings by noting it includes dead sessions, which is a key distinction from session manipulation tools like close_session or send_command.

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 doesn't explicitly say 'use this when,' but it clearly implies list_sessions is the entry point for inspecting sessions. It provides next-step guidance: dead sessions can be accessed via get_snapshot() and cleaned up using close_session(). This gives context on when to use the tool relative to siblings.

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