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

Goes well beyond the readOnly/idempotent annotations by disclosing the pagination contract, the mandatory post-reassembly integrity check, the warning that unknown archive status never proves ingestion/reading/analysis/approval, the failure modes for expired/changed/inaccessible originals, and a security instruction to treat contents as untrusted evidence on a copy.

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-loads what is read and the page mechanics, then layers constraints. Every sentence carries information, though the telegraphic fragments ('No access is granted.') and the trailing security note make it slightly dense rather than maximally clean.

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 usefully covers the return shape (base64 pages, offset-for-continuation, whole-file hash) plus failure and integrity behavior. Minor gaps remain around the two required ID parameters and any rate/permission limits, but nothing critical to correct invocation is missing.

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 only 25% across 4 parameters. The description compensates partially by explaining the offset continuation loop and the 64 KiB page ceiling (maxBytes), but importId and projectId semantics are left entirely to the schema, so it does not fully close the coverage gap.

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 ('Read the actual archived source original for an import in this dossier') and immediately distinguishes it from excerpt/page siblings by emphasizing the 'actual archived source original' and its base64 page delivery. An agent can tell this apart from helvabase_read_source_excerpt_page or read_original_page without opening either 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?

Gives concrete operational guidance: page in at most 64 KiB, continue with offset until null, then verify the full SHA-256 after reassembly. It also scopes availability/expiry semantics. It does not, however, name an explicit alternative sibling or a when-not-to-use condition, so it stops short of a 5.

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