terminal_list

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

No annotations are provided, so the description must convey the tool's behavioral profile. 'List' implies a read-only operation, and the described output fields add useful specificity, but the description does not disclose potential limitations, session scoping, or whether the list is global to the workspace.

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 a single efficient sentence with no filler. The main action and resource are front-loaded, followed by a compact list of the returned fields.

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, the description provides sufficient context: it names the return contents and the target resource. There is no output schema, so slightly more detail about the response structure could help, but the core invocation needs are fully covered.

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 zero parameters, so the baseline is 4 and parameter semantics are not a concern. The description adds value by clarifying what data is returned for each session, even though no input semantics are needed.

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 states a specific verb ('List') and a clear resource ('all active terminal sessions'), and enumerates the returned fields: names, PIDs, working directories, and current commands. This differentiates the tool from mutating siblings like terminal_close and terminal_send.

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 implies the tool is for enumerating active terminal sessions, but it does not explicitly say when to use it versus alternatives such as terminal_snapshot or terminal_read. No exclusions or sibling comparisons are provided, so the usage context is only inferred.

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