replay_sessions

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It states 'List recent sessions' but does not clarify that this is a read-only operation, how 'recent' is defined (e.g., sorted by creation time), or any other behavioral traits like pagination or response format. The description is insufficient for an agent to understand the tool's side effects and constraints.

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 sentence that is direct and efficient. It lists the key fields without unnecessary elaboration. Every word contributes to the purpose. No wasted space.

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?

The description is minimal for a simple tool with one parameter and no output schema or annotations. It covers the basic purpose and returned fields, but omits ordering, pagination, read-only nature, and relationship to sibling tools. It is adequately complete for a trivial list operation but leaves gaps that an agent might need to infer.

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% (the single 'limit' parameter has a clear description). Baseline is 3. The description does not add additional meaning beyond the schema; it does not explain how the limit parameter interacts with 'recent' ordering or what the default behavior is. No extra value, but schema covers it adequately.

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 verb 'list' and the resource 'sessions', and further specifies the fields included (status, model, duration, checkpoint count). This distinguishes it from siblings like 'replay_status' (which likely shows a single session's status) and 'replay_stats' (aggregated statistics). However, it does not explicitly differentiate from 'replay_search', which might also list sessions but with additional filtering criteria.

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 alternatives. No explicit conditions, prerequisites, or exclusions are provided. The implied use is for listing recent sessions, but without context on when to prefer this over 'replay_search' or 'replay_status'.

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