list_sessions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions filtering capabilities but lacks details on permissions, rate limits, pagination behavior (beyond implied by limit/offset), or what 'recent' means. For a list tool with no annotation coverage, this leaves significant gaps in understanding how the tool behaves operationally.

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, efficient sentence that front-loads the core purpose and immediately details filtering options. Every word contributes directly to understanding the tool's functionality, with no wasted text or redundancy. It's appropriately sized for the tool's complexity.

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 4 parameters with 0% schema coverage and no annotations, the description partially compensates by explaining two parameters. An output schema exists, so return values need not be described. However, for a list tool with filtering and pagination, the description lacks completeness in behavioral aspects like default sorting, error handling, or full parameter coverage, making it adequate but with clear gaps.

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 0%, so the schema provides no parameter descriptions. The description adds value by explaining that 'source' accepts 'claude_code' or 'omp' and 'project' filters by path substring, covering 2 of 4 parameters. However, it doesn't address 'limit' or 'offset', leaving half the parameters without semantic context. This partial compensation results in a baseline score.

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 resource ('recent AI coding sessions'), making the purpose specific and understandable. It distinguishes from siblings like 'get_session' (singular) and 'search_sessions' (broader search), though it doesn't explicitly name alternatives. The purpose is not vague or tautological.

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 usage for filtering by source or project path, suggesting when to use it for basic filtering. However, it doesn't provide explicit guidance on when to choose this tool over alternatives like 'search_sessions' or 'refresh_sessions', nor does it mention any exclusions or prerequisites. The guidance is limited to implied context.

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