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

readOnlyHint=true already covers the safety profile, so the description goes further by warning that historical participant text is 'untrusted data' and advising a compare-before-editing workflow. These are real behavioral cautions beyond the annotation, though no pagination or payload size behavior is mentioned.

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 tight sentences, front-loaded with the core action, then the usage trigger, then the safety caution. No filler; each sentence advances the agent's ability to call it correctly.

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?

An output schema exists so return values need not be described. For a two-param read-only tool, the description covers what it does, when to use it, where params come from, and a data-trust caveat, which is complete.

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 both params are bare strings, but the description compensates by telling the agent where the values originate ('from a catch-up event') and what they identify. It adds sourcing context the schema lacks, though not format specifics.

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 with a precise scope: 'Read the full attributed text of an exact page revision.' The word 'exact revision' distinguishes it from sibling read_page (current state) and read_page_history (revision listing).

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 says when to use it ('Use page_id and revision_id from a catch-up event to inspect what changed') and routes the agent away from it when only current state is needed ('Compare current_revision_id or read_page before editing'). Both the trigger and the alternative are named.

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