list_sessions

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

Annotations already declare this tool read-only and idempotent. The description adds useful context by specifying it targets local sessions of the same project and is a precursor to fetching body text, but it does not disclose return format, pagination behavior, or how session selection works.

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 focused sentence that front-loads the tool's purpose and immediately states its intended position in the workflow. There is no redundancy or 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?

For a tool with four parameters, no output schema, and a need to guide an agent through the selection-to-read flow, this description is too thin. It does not explain what the tool returns, how to choose a session, or how the result feeds into read_session, so an agent may struggle to invoke it correctly.

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?

Schema coverage is only 50%, and the description adds no parameter-level meaning beyond what the schema already provides. The 'same project' phrasing loosely maps to projectPath, but limit and offset remain undocumented in both schema and description, so the description does not compensate for the gap.

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 and resource: it finds and selects local sessions for the same project. It also adds sequencing context ('use before fetching the body'), which helps distinguish it from read_session, though it does not explicitly differentiate it from prepare_handoff.

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 gives clear usage context: it should be used before fetching session body content. However, it does not state when not to use it or explicitly name alternatives, leaving some inference to the agent.

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