opencode_session_list

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

With no annotations provided, the description carries the full behavioral burden, and it discloses almost nothing: no statement that this is a read-only operation, no pagination or result-limit behavior, and no indication of what a session record contains. 'List all sessions' leaves the agent to infer the safety profile and result shape.

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 short, front-loaded sentence with zero waste. It is efficient, though arguably under-specified rather than genuinely concise given what a session-list tool needs to convey.

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 listing tool with no output schema, the description should at minimum indicate the scope of returned data or pagination behavior. Instead it is a bare four-word sentence, leaving return format and result limits entirely undocumented.

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%, so the directory parameter and its default behavior are already fully documented in the schema. The description adds no syntax, format, or semantics beyond that, so the baseline 3 applies; if anything, 'all sessions' slightly obscures the existence of the filter.

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 names a clear verb and resource ('List all sessions'), so the basic action is unambiguous. However, it does nothing to distinguish this tool from siblings like opencode_session_search, opencode_session_get, or opencode_sessions_overview, and the word 'all' is arguably misleading given the schema's optional directory scoping filter.

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 guidance on when to use this tool versus the many adjacent session/overview/search tools. No prerequisites, no mention of how it relates to opencode_sessions_overview, which sounds functionally overlapping.

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