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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a concrete behavioral constraint with 'Max 1000 per call,' though it does not state what happens when the limit is exceeded (error vs truncation).

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 short sentences with no filler. The verb and object are front-loaded, and the constraint 'Max 1000 per call' is placed in its own terse sentence that earns its place.

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 simple, safe, optional-range read operation with fully documented parameters and non-destructive annotations, the description is nearly complete. It is missing only explicit return-shape or error behavior and a named pointer to sibling tools for single-receipt reads.

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% and both parameters already have clear defaults and meanings, so the baseline is 3. The description adds value by introducing the range limit, which gives additional semantic weight to from_serial and to_serial as a bounded interval.

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 description states a specific verb ('Read'), a distinct resource ('a range of receipts'), and a clear purpose ('audit chain continuity'). This range-based scope differentiates it from sibling tools like vigil_get_receipt, which implies a single receipt.

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 gives clear context for when to use the tool: when auditing chain continuity over a receipt range. The 1000-per-call max is a useful boundary, but it does not explicitly name alternatives or when-not-to-use conditions, so it falls 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.