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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds genuinely non-derivable context: the returned HTML is untrusted data and must not be treated as instructions, and that no modification/restore occurs. It stops short of saying how out-of-range or pruned revisions 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?

Three tight sentences, front-loaded with the read scope, then the security constraint, then the non-mutation guarantee. Nothing is padding and nothing repeats the title or annotations.

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 correctly signals what comes back (original HTML) and, importantly, how to treat it. It is close to complete for a two-parameter read tool; the remaining gap is sourcing the revision id and out-of-range behavior.

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%, so the description carries the burden for both parameters and largely doesn't: it names 'revision' but never explains the positive-integer constraint, where the revision identifier comes from, or that 'id' refers to the owned page identifier. The only implicit hint is the word 'owned page'.

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 precise verb+resource+scope: read original HTML from one retained revision of an owned page. It is clearly distinguishable from siblings list_revisions (enumerate) and restore_revision (mutate), so an agent can select it without opening other schemas.

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 'one retained revision of an owned page' implies the preconditions (ownership, retention) and the singular-revision constraint, which is real usage signal. However it never names the sibling that yields the revision identifier (list_revisions) or states what to do when a revision is no longer retained, leaving the when-to-use path incomplete.

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