list_sessions

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so safety is covered by structured data. The description adds nothing beyond that — no indication of what is returned, whether sessions are live processes or stored records, or how the list is scoped; the word "Open" only adds ambiguity about whether anything is being opened.

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 single fragment is short but under-specified rather than concise — it spends its three words without conveying the listing behavior that the name implies. Brevity here costs comprehension instead of saving it.

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?

An output schema exists, so return values need not be explained, and the annotations fully cover the safety profile. Even so, for a tool sitting among start_session, read_session, stop_session, and stop/restart siblings, the description does not establish enough to select it confidently.

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, so there is no parameter meaning to add and the baseline of 4 applies. The description does not misuse or misdescribe any inputs.

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?

"Open process sessions" supplies a verb and a resource, but the verb is wrong for a tool named list_sessions and reads as a tautology-of-sorts rather than a listing operation. An agent cannot tell from this sentence whether it enumerates sessions or opens one, and it is not distinguished from start_session, read_session, or stop_session.

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?

There is no when-to-use guidance at all: no statement of what a "session" is here, no prerequisite, and no pointer to start_session/read_session/stop_session as the alternatives for acting on a single session. The agent must infer usage entirely from the tool name.

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