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

Annotations already declare readOnlyHint=true, but the description adds genuine behavioral context beyond them: the data is untrusted citizen-authored, the CallToolResult _meta carries a server-owned provenance boundary, and empty results have a specific meaning. The trailing read-only restatement duplicates the annotation, but the provenance/trust disclosures are real added value.

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 tight sentences, front-loaded with what is read, then result semantics, then trust/safety. Little waste, though the final READ-ONLY clause partially repeats the annotation.

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 characterizes the return (chained/checkpointed register and rotation events, untrusted authorship, provenance boundary) and the empty-result case. It omits pagination/volume characteristics but is otherwise complete enough for a simple 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% for the single 'id' parameter, so the schema already carries the semantics. The description adds nothing further about the id (e.g., where to obtain it), so the baseline of 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 ('one witness pointer's register and key-rotation events'), which is concrete enough to separate it from a generic 'history' read. However it never names or contrasts against the obvious nearby siblings (witnesses, history, citizen_keys), 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?

The description gives no explicit when-to-use, when-not, or alternative-tool guidance. The only conditional information is a data-semantics note ('An empty history means not recorded, not that nothing happened'), which helps interpret results but does not route tool selection.

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