list_sessions

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

With no annotations, the description carries the full behavioral burden but only discloses sort ordering ("Live agents first"). It says nothing about default filtering of archived sessions, result format, pagination, or why a session might be omitted, all of which matter for a 7-parameter listing tool.

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?

Two short sentences, front-loaded with the resource and scope, with zero filler. It is efficient, though the terseness trades away useful detail rather than being genuinely information-dense.

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 7-parameter tool with no annotations and no output schema, the description is thin: it omits default behavior for include_archived/live_only, how filters combine, and what a returned session record contains. An agent could call it, but only by guessing at defaults.

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 43%, so the description must compensate, yet it adds meaning only for the `agent` parameter by restating the supported agent names. The remaining parameters (cwd, limit, query, branch, live_only, include_archived) receive no explanation or interaction semantics beyond what the schema already says.

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?

States a specific verb and resource ("List ... sessions") and enumerates the eight agent families it covers, so the scope is unambiguous. It does not differentiate itself from siblings like get_session or session_digest, so the agent must infer the singular-vs-list distinction from the names alone.

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 no when-to-use guidance, no prerequisites, and names no alternative. "Live agents first" describes result ordering, not the conditions under which this tool should be chosen over get_session or session_digest.

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