delimit_handoff_list

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only nature, destructive potential, authentication needs, or rate limits. The description only states the basic function without any safety or operational context.

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 extremely short (two words plus parenthetical), but this brevity comes at the cost of missing critical information. It is under-specified rather than appropriately concise, as it fails to convey enough detail for effective tool selection.

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 the presence of an output schema (not shown) and a simple parameter set, the description still lacks context about what constitutes a 'receipt', how results are ordered or paginated, and any filtering behavior beyond the status parameter. The tool is not fully explained.

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?

The input schema fully describes the single parameter 'status' with its default and allowed values. The description adds no additional meaning beyond what the schema already provides. With 100% schema coverage, the baseline of 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 action ('List') and the resource ('handoff receipts'). It also notes '(Pro)' suggesting a tier restriction, which provides additional context. Among sibling tools like 'delimit_handoff_create' and 'delimit_handoff_acknowledge', it distinguishes itself by focusing on listing receipts.

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 provides no guidance on when to use this tool instead of alternatives. It does not mention any prerequisites, contexts, or exclusions. The agent is left to infer usage from the name and sibling tools.

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