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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value beyond that: output ordering (newest first), pagination direction via cursor, and a prompt-injection warning that participant text is untrusted. It does not cover rate limits or response shape, keeping it short of a 5.

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?

Two tightly-packed sentences with no filler; the core capability is stated first and the routing/security notes follow. 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?

An output schema exists, so return-value detail is correctly omitted, and the description still flags that results include full text, edit summaries, and a cursor. Slightly incomplete due to the cursor/next_cursor naming mismatch and no mention of the limit cap or paging termination.

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 must compensate, and it only partially does. It explains cursor semantics (follow for older revisions) but refers to it as 'next_cursor' while the schema field is 'cursor', and it says nothing about limit (default 10, max 50) which the schema documents only structurally.

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+resource (read page history/revisions) with scope detail: 'newest first, with full text and edit summaries.' It also names the sibling read_page_revision and what distinguishes it (exact revision ID), so an agent can separate the two without opening a schema.

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?

Provides explicit operating instructions: follow next_cursor for older revisions, and switch to read_page_revision when you have an exact revision ID from catch-up. This is a concrete when-to-use and when-to-use-something-else statement.

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