list_sessions

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

With no annotations available, the description carries the full burden. It discloses several behaviors: newest-first ordering, automatic flow selection when flowId is omitted, and the specific return fields (sessionId, sessionStatus, outcome, createdAt) including all possible status values. This is far beyond a generic 'list sessions' statement.

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 three sentences, each serving a distinct purpose: what it does, how it behaves, and when to use it. No redundant or extraneous information.

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 no output schema, the description effectively documents the return shape and statuses. It also covers ordering, fallback logic, and the next-step usage with get_session, making it complete for a simple list tool.

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% for both parameters. The description adds only a reiteration of the flowId fallback (already in the schema) and does not provide additional parameter-level insights. Baseline 3 is appropriate.

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 'List verification sessions for a flow, newest first' – a specific verb and resource. It also explains the primary use case (finding a sessionId to pass to get_session), distinguishing it from sibling tools like list_flows and create_session.

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?

Explicitly instructs when to use this tool: 'Use this to find the sessionId of a session you just created, then pass it to get_session for full detail.' It also notes the automatic fallback to the account's first flow when flowId is omitted, providing clear context for usage.

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