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

It explains the surprising readOnlyHint=false: this "read" persists a receipt and "a write scope is required for audit receipts." It further discloses that no mutation-result cache stores source content, that replay does not count twice, that history is preserved across restarts, and that source text is untrusted evidence. This is rich behavioral context well beyond what the annotations provide.

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?

The purpose is front-loaded, but the body is a dense, telegraphic run-on of interleaved caveats with no headings or grouping. Almost every clause carries information, yet the poor structure makes the operative instructions hard to parse at a glance.

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 7-parameter, nested-object, no-output-schema tool, the description covers the retry/replay/restart lifecycle, write-scope requirement, and OCR consent. It omits what "bounded" means (page limits) and the broader return shape, but the core decision-relevant context is present.

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?

With only 14% schema description coverage, the description has to carry parameter meaning and largely does: it maps sourceKey/contextRevision/readRevision (expectedReadRevision) to the revision workflow, covers restart ("Restart explicitly after source changes"), and enableOcr (explicit consent). It leaves projectId and the required-object formats unexplained, so it compensates substantially but not fully.

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 first sentence states a specific verb and resource: "Return a bounded Snipara document page and persist only its receipt," which tells the agent this reads a single paged document plus writes a receipt. However, it does nothing to distinguish itself from the many sibling readers (read_source_original, read_source_excerpt_page, inspect_original, read_client_original), and "Snipara" is unexplained jargon.

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?

The description gives substantive procedural context: start with expectedReadRevision=null then move to the latest revision, read coverage/receipts after a timeout and replay the exact pageRevision, restart explicitly after source changes, and OCR requires explicit customer consent. It stops short of naming alternative tools to use instead, so it is clear context without explicit exclusions.

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