delimit_handoff_list

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

No annotations provided, but the description declares the tool is read-only ('Side effects: read-only') and notes it calls ai.handoff_receipts.get_receipts. This compensates for missing annotations, though lacks detail on potential rate limits or data freshness.

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?

Succinct and well-structured: purpose first, then usage guidelines, sibling contrast, and side effects. Every sentence adds value without extraneous 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?

Given a single optional parameter with full schema coverage and an existing output schema (implied by context), the description covers all needed behavioral and contextual information.

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% for the single parameter 'status', which has a clear default and description. The description does not add additional context beyond the schema, so 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 the tool lists session handoff receipts, distinguishing it as a read operation. It specifies 'List session handoff receipts (Pro)' and contrasts with sibling tools that create or acknowledge handoffs.

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 states when to use (at session start, to audit acknowledged handoffs) and when not to use (to create or acknowledge handoffs), with direct references to alternative tools delimit_handoff_create and delimit_handoff_acknowledge.

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