list_sessions

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

The description does not explicitly confirm that the tool is read-only or non-destructive, and no annotations are provided. However, the word 'list' implies a safe operation, and specifying 'alive and dead' adds some context about the data scope.

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?

Single sentence, no wasted words. The verb 'List' is front-loaded, making the purpose immediately clear.

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?

Given the simplicity of the tool (no parameters, list operation), the description is largely complete. It specifies the scope and that both alive and dead sessions are included. However, it lacks details about output format or behavior when no sessions exist.

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?

There are zero parameters, so the baseline is 4. The description adds value by clarifying the scope ('alive and dead') beyond the empty schema, though it doesn't need to explain parameters.

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 sessions (both alive and dead) in the project. The verb 'list' and resource 'sessions' are explicit, and it differentiates from sibling tools like 'list_modules' or 'list_notes'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'resume_session' or other listing tools). There is no mention of context, prerequisites, or when not to use it.

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