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

The description frames this purely as a read ('Retrieve', 'Read source IDs and versions; no generated facts'), yet annotations declare readOnlyHint=false and destructiveHint=true. Nothing in the description accounts for a destructive, non-read-only operation, so the read framing directly contradicts the annotations' safety profile.

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?

Purpose is front-loaded and the whole thing is a tight cluster of sentences with no filler. The 'Jev classification' phrasing is jargon that costs some readability, keeping it from a 5, but overall it is efficient.

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 4-param tool with no output schema it discloses return content ('source IDs and versions'), scope limits ('encrypted content excluded'), and a cursor caveat, which is decent. However it never explains the destructive/non-read-only side effects implied by the annotations, leaving the most consequential behavioral question unanswered.

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 already 75%, but the description adds genuine meaning beyond it, most notably that 'since_seq is a message sequence (not the event cursor) and labels the resumption point' — an important disambiguation the schema does not provide. It also clarifies the 'objective' is passed to a semantic provider (reinforcing the schema note).

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 ('Retrieve') and a concrete resource ('bounded accessible message/page/request/task evidence') scoped 'for a room resumption or objective.' This is clear enough that an agent can distinguish a unified cross-type evidence fetch from the component-specific siblings (messages_search, task_context_list, page_get). It stops short of naming which sibling it replaces, so it is not a 5.

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 'for a room resumption or objective' implies the usage context, and 'since_seq ... labels the resumption point' reinforces it, but there is no explicit when-to-use/when-not and no alternative named (e.g., versus messages_search or task_context_list). Usage is inferable rather than directed.

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