List zcode sessions

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It says 'List recent zcode sessions' which implies a read-only, non-destructive operation, but it doesn't explicitly state that there are no side effects, no permissions required, or any rate limits. It does disclose the output fields, which is helpful, but lacks explicit behavioral detail for a listing operation.

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?

A single sentence that is front-loaded with the primary purpose, followed by a direct tie-in to its output's use in zcode_run. No wasted words; every clause adds value. The structure is clean and immediately scannable by an agent.

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 there is no output schema, the description compensates by naming the returned fields (id, title, directory) and explaining how they are used (as session_id). It also mentions 'recent', implying a limited or time-ordered set, though it doesn't specify a count or ordering. For a simple list tool with one optional parameter, this is nearly complete; a note on whether it returns an array or object would push it to 5.

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 description coverage is 100%, and the cwd parameter has a clear description ('Workspace directory to list sessions for (default: server cwd)'). The tool description adds no additional meaning beyond what the schema already provides; it only reiterates the workspace context. Baseline 3 applies since the schema handles the parameter documentation.

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 action (list), the resource (zcode sessions), and the returned fields (id, title, directory). It also notes the workspace scope, which distinguishes it from siblings like zcode_run (executes sessions) and zcode_check (presumably checks something else). This is specific and unambiguous.

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 explicitly states that the output is usable as session_id in zcode_run, giving a concrete use case and linking it to a sibling. It implies this is the tool to call before running a session, but doesn't explicitly say when not to use it or mention alternative conditions. Clear context with no exclusions.

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