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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds a material behavioral fact not in the structured data: the call is metered and paid per invocation via x402. It also discloses the shape of the result (ordered events + integrity check). It stops short of describing pagination or what the integrity verdict looks like on failure.

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 sentences, no filler, and the primary payload (ordered history plus integrity check) is front-loaded ahead of the billing note.

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 the return and does so (ordered events, fingerprints, chain integrity), and it flags the payment requirement. What is missing is any hint about result size, ordering guarantees, or error behavior.

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?

There is one required parameter with 100% schema description coverage, so the schema already carries the semantics. The description only alludes to it via 'for a lot' and adds no format, validation, or naming guidance beyond the schema.

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+resource: returns a lot's full ordered event history with per-event fingerprints plus a whole-chain integrity check. That is clearly distinguishable from privi_record_event and privi_lookup_fingerprint, though it does not explicitly name privi_verify_lot, which sounds like the nearest sibling.

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 implies the usage context (you want the complete ordered history and a chain-level integrity verdict), but gives no explicit when-to-use guidance, no exclusions, and no comparison against privi_verify_lot, whose scope may overlap.

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