List persistent SSH sessions

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

Annotations already declare readOnly/idempotent/destructive hints, so the description adds value by specifying the exact fields returned and the 'live session' scope. The mention of 'idle-reap countdown' provides extra lifecycle context beyond what annotations convey, though it does not detail the output format or pagination.

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 two sentences with zero filler. It front-loads the core action, then packs in specific return fields and a critical usage reminder. Every word 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 simple list tool with no parameters and no output schema, the description fully covers behavior, return field details, and usage instructions. The agent knows exactly what to expect from the call and how to apply it, making the tool self-contained.

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 tool has no parameters, and the schema is empty, so the baseline is 4 per the rubric. The description accurately reflects the parameterless nature and adds no unnecessary parameter details. Nothing is needed beyond the baseline.

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 all live SSH sessions with a specific set of fields (host, cwd, state, etc.). This distinguishes it from sibling tools that open, run, interrupt, peek, or close sessions. The verb 'list' unambiguously defines the action.

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 explicitly directs users to use this tool to recover valid session ids and warns against inventing ids, which is crucial for safely using other ssh commands. It lacks an explicit 'when not to use' or alternative comparison, but the context of the sibling tools makes the use case clear.

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