list_terminal_sessions

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's real addition is the `session` handoff convention, but it says nothing about ordering, whether results span windows/workspaces, or freshness of connection state — modest value on top of structured fields.

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, no filler. The resource and scope are front-loaded, and the cross-tool identifier note follows immediately.

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?

With an output schema present, the description need not explain return values, and the enumerated fields are a reasonable hint. It is nearly complete, but an agent still cannot tell whether the list is scoped to a window/workspace or how large it might be.

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 takes zero parameters, which is the baseline-4 case. The description correctly offers no parameter guidance and instead explains how the values this tool returns are consumed as `session` elsewhere.

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?

States a specific verb and resource ("List terminal sessions open in Termius") and narrows the scope to SSH and local tabs, which implicitly separates it from list_sftp_sessions and list_hosts. It stops short of naming the sibling it is not, so an agent must infer the boundary rather than read it.

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 second sentence gives concrete downstream guidance: any of id prefix / name / address can be passed as `session` to the other tools, which tells the agent to call this first to obtain an identifier. There is no explicit when-not or a named alternative, so it falls short of a 5.

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