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

With no annotations provided, the description fully carries the behavioral burden and does so excellently. It discloses the side effect of marking handoffs as delivered, the 24-hour disappearance from the default view, and clarifies that the content is data, not instructions. This is exactly the kind of behavioral detail an agent needs to avoid data loss.

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?

Although the description is long, every sentence earns its place: purpose, distinction, side-effect warning, data-not-instruction warning, filter details, and config override. The 'IMPORTANT:' marker highlights the most critical behavioral trap, and the structure is logical and front-loaded.

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 no annotations, no output schema, and a serious side effect, the description covers all essential operational aspects: what it lists, the consumption behavior, the filter options, and the projectName override. An agent can call it correctly and understand the consequences without additional 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?

The description adds significant meaning to the filter parameter by explaining what each enum value returns ('open' = unresolved not delivered in 24h, 'mine' = only addressed to you, 'all' = everything including resolved). For projectName, it gives a concrete precedence rule but does not explicitly define what the parameter represents, leaving some ambiguity.

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 states the specific action 'List handoffs' and defines the resource as 'markdown notes from teammates addressed to you or the whole project.' It also distinguishes the tool from tasks ('Not tasks') and, by implication, from single-handoff tools like get_handoff and resolve_handoff, making the purpose unmistakable.

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 strong usage guidance: it warns that calling marks handoffs as delivered and instructs the agent to relay everything immediately. It also explains the filter semantics and the projectName config preference. However, it does not explicitly name an alternative for retrieving a single handoff (e.g., get_handoff), only excluding tasks.

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