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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds genuinely non-derivable context: the packet is bounded, 'the work revision is not an all-knowledge cursor,' and inspection of citations/truncation/omissions is required because 'observations are not verified conclusions.' That is real behavioral value beyond the annotations.

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?

Three sentences, front-loaded with the packet scope before caveats. Most content earns its place, though the final sentence packs several distinct warnings ('source citations, truncation, omissions... not verified conclusions') somewhat densely.

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 no output schema, the description carries the burden of describing returns, and it does so by enumerating the packet contents plus truncation/omission caveats. It is largely complete for an agent to call the tool correctly, missing only a fuller statement of when to prefer it over get_orbit_overview or get_orbit_timeline.

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 coverage is 67%, so the schema already documents task_id and max_chars in useful detail. The description adds the notion of a 'bounded' packet and clarifies that the revision is not a knowledge cursor, but it does not explain orbit_id or the task_id vs. topic-wide scoping tradeoff in its own text, so it adds only marginal value over the schema.

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 ('Read') and resource ('bounded task-work context packet') and enumerates its contents (tasks, attempts, checkpoints, handoffs, leases, evidence references). It also distinguishes itself from siblings by naming what it excludes and pointing to search_contributions and search_previous_work for those cases.

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?

Explicitly states when-not-to-use-it ('Excludes revisioned contributions and legacy memories') and routes the agent to the two alternative tools. It does not, however, contrast with adjacent siblings like get_orbit_overview or get_orbit_timeline, so the when-to-use-this case is implied rather than fully spelled out.

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