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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds the digest-verification precondition and the 'one exact page' paging notion, but doesn't say what happens on digest mismatch, how errors surface, or how large a page is.

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?

A single dense sentence that front-loads the action and then the precondition. Every clause carries information, though the phrasing is jargon-heavy enough to slow a first read.

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 tool with a nested object parameter, 0% schema coverage, no output schema, and a digest-verification step, the description is too thin. It never defines what a handoff is, what the evidence page contains, or how verification failure is communicated, so an agent cannot fully predict call outcomes.

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 0% and one parameter (handoff) is an undocumented nested object, so the description carries the full burden. It gestures at 'handoff', 'source digest', and paging via 'one exact evidence page', but never explains what sourceId identifies or what offset does, leaving the core inputs ambiguous.

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?

States a specific verb and resource ('Read one exact evidence page from a ResearchPilot handoff'), which is concrete enough to act on. It doesn't explicitly differentiate from nearby siblings like researchpilot_read_work_artifact or researchpilot_handoff_summary, so an agent must infer which retrieval path applies.

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 clause 'after verifying the outer source digest against the immutable ResearchContext snapshot' gives a precondition for use, which is genuinely useful. However, there is no guidance on when to choose this over read_work_artifact or handoff_summary, and no statement of when it should not be used.

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