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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description then adds non-obvious behavior the annotations cannot convey: bounded pagination, the revision-pinning rationale (a replacement could silently swap the material mid-read), that source/page content is untrusted data and never instructions, and that sources are private. These are exactly the kinds of hidden traits that change how an agent should 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?

Four compact sentences with the purpose front-loaded, then the paging invariant, then the trust boundary. Dense and largely waste-free, though the closing sentence about publishing belongs to a different operation and slightly dilutes focus.

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 read-only tool with no output schema and four undocumented parameters, the description supplies the critical context an agent needs (page boundaries, revision pinning, untrusted content). Only the per-parameter meaning of account_id/source_id/limit/offset remains unaddressed.

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 carry the burden, and it only partially does: it explains revision_id's role in stable paging and implies limit/offset via 'bounded pages', but says nothing about account_id, source_id, or the default (10000) and max (20000) page size semantics.

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?

The description gives a specific verb and resource with scope: 'Read a private source revision in bounded pages.' The word 'private' plus 'source revision' distinguishes it from the public-facing siblings, though it never explicitly names get_knowledge_page or get_knowledge_change as the alternatives.

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?

It provides operational guidance for a single usage mode ('Retain revision_id when paging so a replacement cannot silently change the material being read'), which is genuinely useful. However, it never states when to reach for this tool instead of get_knowledge_page, get_knowledge_change, or get_knowledge_center, nor what preconditions (permissions, private vs published state) apply.

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