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

With no annotations, the description carries the full burden and does so substantively: it discloses the access-control model (owner sees the full row, everyone else gets a hash-only subset), the current limitation that owner retrieval is pending so all callers get the hash-only view today, and expected latency. It omits error behavior for malformed/unknown ids, which keeps it from a 5.

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?

Purpose is front-loaded, sections are labeled and skimmable, and every block (inputs, returns, latency) carries non-redundant information. The returns enumeration is list-heavy but justified given there is no output schema to fall back on, so it reads as dense rather than padded.

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?

Given no annotations and no output schema, the description supplies the return shapes (owner vs public field lists), access rules, latency, and the pending-owner caveat — enough for an agent to call it and interpret the result. The remaining gap is guidance on failure modes and how to choose it over the similar receipt/verify siblings.

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%, so the description must compensate for the single parameter — and it does, specifying that receipt_id is a path parameter, required, and constrained to the GR-YYYY-NNNNNNN format. That format constraint is genuine added meaning beyond the bare string type in 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 (retrieves) and resource (a previously-issued signed GhostRoute receipt) with an exact id format and stated goal (independent audit of a past sovereignty verdict). It is clear on its own, but with many near-identical siblings (get_receipt, receipt_lookup, verify_receipt) it never explains how it differs from them, so it stops short of full sibling differentiation.

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 explicit 'Use this tool when:' block gives two concrete trigger scenarios (holding a receipt id to confirm contents/signature, reconciling an action log against the attestation layer), which is well beyond implied usage. It offers no when-not conditions and names no alternative among the many receipt-related siblings, so it does not reach a 5.

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