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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context beyond annotations by revealing that omitting the status filter returns only open and accepted handoffs by default, which is non-obvious and important for correct invocation.

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?

Two short sentences, no filler, and the core behavior is front-loaded in the first sentence. Every sentence earns its place by stating either the primary action or an important default behavior.

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 simple read-only list tool with one optional parameter, the description plus schema and annotations are complete. The default filter is disclosed, the parameter values are in the schema, and the safety profile is carried by annotations, so nothing essential is missing for an agent to invoke it correctly.

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 100% and the status parameter is fully documented with its allowed values ('open, accepted, done, cancelled, or all'). The description adds no additional parameter-level meaning beyond what the schema already provides, so the baseline score 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 states a specific verb ('Returns'), a clear resource ('handoffs'), and a filtering dimension ('status'), making the tool's purpose immediately distinguishable from siblings like vault_list_conflicts or vault_search_projects. The title aligns with the description, leaving no ambiguity about what is listed.

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 use when a caller wants a list of handoffs, and it gives useful default behavior (open and accepted), but it never explicitly contrasts this tool with alternatives like vault_get_context or vault_search_projects. There is no exclusion or when-not-to-use guidance, so the agent must infer appropriate usage.

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