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

Annotations only cover the safety profile (readOnly, idempotent, not openWorld). The description goes well past that by disclosing partial-failure semantics: nonexistent paths land in `missing` instead of failing, overflow beyond 20 lands in `remaining`, and truncated pages land in `omitted` with sizes. That is exactly the behavior an agent needs to reason about a 3-way partial result.

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?

Front-loaded with the core action and scope, and the trailing clauses about `missing`/`remaining`/`omitted` all carry distinct information. It is dense and slightly run-on, but no sentence is wasted.

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 carries the return-shape burden and does so by naming the three outcome buckets (missing, remaining, omitted) and the default char budget. Given only two well-documented parameters and read-only annotations, nothing material is left unexplained.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the consequence of `maxChars` (pages past the cap are surfaced in `omitted` with their sizes) and reinforcing the 1-20 bound on `paths`. It does not restate the min/max numeric bounds, but the semantic effect is documented.

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 (batch read pages of the Radix Wiki) with an explicit scope bound (1 to 20, in full, one call). It also differentiates itself from sibling read paths by naming it as how to read search or listing results.

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 clearly positions itself relative to search_wiki and list_pages output ('which is how to read search or listing results'), telling the agent when to reach for it. It stops short of explicitly naming get_page as the single-page alternative, so the single-vs-batch choice is only implied.

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