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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two genuinely new behavioral facts: the output excludes source bodies and validation is anchored to the original handoff package. It stops short of saying what 'outer identity' validation actually checks or what a failed validation looks like.

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 tightly packed sentences with the action front-loaded and no filler. It is dense to the point of jargon ('outer ... identity'), but every clause carries information and nothing is redundant.

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?

With a nested object parameter at 0% schema coverage, no output schema, and no annotations-specific gaps to hide behind, the description should define the handoff package shape and the summary's bounds. It gestures at both ('bounded', 'original ... as the authority') without resolving either.

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?

There is a single required parameter, 'handoff', typed only as a bare nested object with 0% schema description coverage and no visible structure. The description says to treat the original handoff package as authoritative but never explains what fields the object must carry or how an 'original' package is distinguished from a modified one, so the agent cannot construct a valid call from the docs.

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 pairs specific verbs with specific resources ('validate the outer ... handoff identity', 'return a bounded context summary'), which is well beyond restating the name. The phrase 'without source bodies' implicitly differentiates it from read_handoff_evidence, though the sibling contrast is only implied rather than named.

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?

'Use the original handoff package as the authority' is a correctness constraint, not usage routing. Nothing says when to call this versus researchpilot_handoff_context, researchpilot_read_handoff_evidence, or researchpilot_validate_specialist_receipt, leaving the agent to infer selection from names alone.

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