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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only that the receipt is 'signed' and tied to an 'execution', which hints at content authenticity but does not disclose any additional behavior (auth requirements, failure modes, or what signing guarantees).

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?

One sentence, zero waste, verb and lookup key front-loaded. Nothing extraneous and nothing structurally awkward.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. However, in a sibling set containing verify_receipt and get_evidence_bundle, the description leaves the retrieval-vs-verification routing question unanswered, which is the main thing an agent still needs.

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 100% with a single required receiptId that is already documented as the 'PriorSeal receipt identifier'. The description's 'by its identifier' merely restates the schema, so the baseline 3 applies.

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 resource ('a signed execution receipt') with the lookup key ('by its identifier'). It is clear on its own, but it does not differentiate from close siblings such as priorseal_verify_receipt or priorseal_get_evidence_bundle, which an agent must disambiguate on its own.

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?

No guidance on when to use this versus verify_receipt, get_evidence_bundle, or the other get_* siblings. The phrase 'by its identifier' implies a lookup precondition but does not state where a receiptId comes from or what makes retrieval the right action.

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