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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description earns credit by disclosing that this register is internal and 'not silently included in buyer documents', plus that results are paged ('Page through all records') — real context beyond the annotations.

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?

Two tight sentences, front-loaded with the resource and scope, with no filler. The scope statement and the paging note each earn their place, though the final sentence reads slightly like an aside rather than a routing or constraint cue.

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 annotations present and no output schema, return values need not be described, and the safety profile is covered. But for a 4-parameter tool at 0% schema coverage with a required nested object, the description leaves parameter usage and the meaning of the revision tuple entirely 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 description coverage is 0% and none of the four parameters are named or explained. The nested revision object (outputJobId + payloadHash) is especially opaque, and neither itemId nor the offset/maxFields paging controls are clarified beyond an oblique 'page through all records'.

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 ('Read') and a precisely scoped resource ('internal field-to-original audit trail for one current produced file'), then enumerates the payload: value hashes, sources, authors, review receipts. It is clear against most siblings, though it does not explicitly distinguish itself from the related-sounding helvabase_read_document_receipts.

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?

Usage is implied ('for one current produced file', 'Page through all records'), which tells the agent this is a single-file audit lookup to be paged. However, no alternative tool is named and no when-not/exclusion guidance is given, leaving the agent to infer routing on its own.

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