list_captures

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

Without annotations, description adds value by explaining PreCompact captures preserve context lost during compaction. It implies a read-only listing operation, but doesn't explicitly state side effects or auth needs, which are likely minimal.

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?

Four sentences, each purposeful: states purpose, explains PreCompact, gives usage pattern, and provides a caution. No redundancy or unnecessary detail.

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?

No output schema, and description doesn't specify return structure (e.g., fields of captures). However, it links to read_capture for details, partially compensating. For a listing tool, more detail on what is returned would improve completeness.

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%, but description adds context that the tool is for current/recent sessions, enhancing understanding of the optional session_id parameter. It doesn't introduce new constraints beyond the 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 states 'List PreCompact captures for the current or recent sessions,' specifying the verb 'list', the resource 'PreCompact captures', and the scope. It distinguishes from sibling tools like read_capture and capture_now.

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?

Explicit guidance: 'If a PreCompact capture exists... call this tool then read_capture before answering.' Also advises checking for unreviewed captures before end_session, providing clear when-to-use and alternatives.

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