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

Adds context beyond annotations: it warns the returned data is untrusted citizen-authored, that provenance is carried in CallToolResult _meta, and that the record is verifiable offline. The 'READ-ONLY' sentence merely restates readOnlyHint=true and destructiveHint=false, but the provenance caveat is genuinely informative.

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?

Three sentences, front-loaded with what the tool reads, followed by the provenance caveat and safety note. Mostly earns its place, though the trailing READ-ONLY clause duplicates what the annotations already declare.

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 usefully enumerates the returned contents (keys, domain bindings, chained events with proofs, attestations, checkpoint) and flags the provenance boundary, which is the key context for trusting the data. Adequate for a simple two-parameter read.

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%, so both 'handle' and 'events_since' are documented in the schema (baseline 3). The description does not add format or semantics for either, though 'chained events' loosely relates to 'events_since'.

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 (one citizen's portable dossier) and enumerates the record's contents. The singular 'one citizen's' implicitly contrasts with the plural list-style siblings like 'citizens', but it never names an alternative, so an agent must infer the boundary.

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 when-to-use/when-not guidance and no routing to alternatives such as 'citizen' or 'citizens'. The only usage-adjacent cue is 'Verifiable offline', which describes a property rather than a selection condition.

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