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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real value: the 40,000-character text cap (a silent truncation an agent must know about) and the fact that OCR text is returned inside an untrusted-data fence, which is important prompt-injection context. It does not say what happens when the id is unknown or whether truncation is signalled in the payload.

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 short sentences, each carrying distinct information (what is returned, when to use it, data provenance), with the return contents front-loaded. Nothing is padded or redundant.

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 burden of describing returns, and it does so reasonably: page record plus capped OCR text, with provenance and fencing noted. A brief note on truncation signalling or the shape of the record would close the remaining gap.

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?

The single 'id' parameter is fully documented in the schema, including the LF-…, LF-…:p7, LF-…:c2 formats. The description only restates that the id comes from a search result, adding no syntax or edge-case meaning beyond the schema, so the baseline 3 applies.

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 concrete verb and resource: fetch one page by id, returning its record plus up to 40,000 characters of OCR text. That is far more specific than the bare name 'fetch'. However, it never distinguishes itself from the sibling get_page, which an agent could reasonably assume does the same thing, so it falls short of a 5.

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?

"Use to read a page found by search" gives a usable trigger condition and points at the search tool. But there are no exclusions and no mention of when to prefer this over get_page or get_issue, which is the main ambiguity an agent faces in this sibling set.

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