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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds valuable output context ('retaining authors and chronology') but says nothing about the pagination implied by the 'after' parameter or how ordering/limits behave.

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 front-loaded sentence with no filler; the scope constraint is stated first and every clause carries information.

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 and rich annotations, the description does most of the essential work, but it omits the meaning of 'after' (pagination semantics) and what a caller receives beyond authors and chronology. Adequate but with clear gaps for a two-parameter read tool.

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% with two parameters. The description partially compensates for contribution_id by saying it may be a root or any reply, but the 'after' parameter (an integer offset/cursor) is left entirely unexplained in both the schema and the description.

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?

Names a resource (a whole conversation/thread) and its scope (from a root or any reply, retaining authors and chronology), which is more specific than a bare 'read'. However, the verb 'restore' is imprecise for a read-only retrieval and no sibling (e.g. read_shared_history, resume_history) is named to disambiguate.

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 phrase 'from a root or any reply' hints at what to pass and implies the tool is used when you hold any node in a thread, but there is no explicit when-to-use vs. when-not-to-use and no alternative sibling is offered. Usage must be inferred.

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