List sessions

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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description adds meaningful behavioral context: sessions are stored in ~/.nodriver-mcp/sessions/, are not cleaned up automatically, and accumulate over time. This informs the agent about persistence and potential storage growth beyond what annotations convey.

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 three sentences, each providing distinct useful information: the command's output, how to use it with load_session, and the storage location/cleanup behavior. It is front-loaded with the main action and contains no filler.

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?

The tool is simple with no parameters, and an output schema exists, so the description need not explain return values. It sufficiently covers what the agent needs to know: what is listed, how to use it, and the persistence context. The sibling-tool context further helps, but the description stands on its own.

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, so the input schema is trivially 100% covered. Baseline for 0 params is 4, and the description does not need to explain parameters. It correctly omits param details and focuses on what the tool returns.

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 the specific verb 'List' with the resource 'saved session files' and details what is shown (name, save time, contents). It clearly distinguishes from sibling tools like save_session and load_session by describing its unique role.

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 provides clear usage context: it shows the filename to hand to load_session, and notes that sessions accumulate because they are never cleaned up automatically. It does not explicitly mention when not to use it or alternatives, but the purpose is evident from the context.

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