list-sessions

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

With no annotations, the description discloses pagination behavior, filtering options, and return of user-friendly messages for empty results. However, it does not explicitly confirm the operation is read-only or safe (no side effects), which is important for an agent.

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 sentences skillfully convey the core purpose, output fields, filtering, and pagination. No superfluous words; the description is front-loaded and efficient.

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 list tool with 3 parameters and no output schema, the description adequately covers inputs and expected outputs, including empty-state behavior. It does not mention sorting or pagination limits, but given the simplicity, it is sufficiently complete.

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 100%, so baseline is 3. The description adds value by explaining that sessionMode filters production/test runs, that pagination is supported, and that the response includes session IDs, status, timestamps, and execution mode, which go beyond the input schema.

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 specifies the tool retrieves a paginated list of execution sessions for a workflow, listing session IDs, status, timestamps, and execution mode. It distinguishes from siblings like get-session (single session) and terminate-entire-session (mutation).

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 implies use for listing sessions and filtering by production/test, but does not explicitly state when to use this tool versus alternatives like get-session or list-workflows. No when-not-to-use guidance is provided.

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