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

Beyond the annotations (which already declare readOnly/destructive/openWorld), the description adds genuinely useful context: the returned data is untrusted citizen-authored content and CallToolResult _meta carries a server-owned provenance boundary. The READ-ONLY sentence largely restates the annotations, but the trust/provenance note is 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?

Front-loaded with the resource ('One mandate'), and every clause describes a real return component. The field enumeration is dense and somewhat run-on, but no sentence is pure filler.

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 does a good job explaining the returned record's structure, and annotations cover the safety profile. However, it leaves the required id parameter unexplained, so an agent cannot call it correctly without guessing the identifier's origin and format.

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 coverage is 0% for the single 'id' parameter, and the description does not compensate: it never says what an id is, where it comes from, or its format. 'One mandate' only loosely implies the id identifies a mandate, leaving the sole parameter effectively undocumented.

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?

The description makes clear this retrieves a single mandate record and enumerates what that record contains (stored text, commit payload, seal/chain event, inclusion-proof link, offline-check recipe). It implicitly contrasts with the plural 'mandates' sibling by scoping to 'one mandate', though it never states the retrieval verb outright.

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 guidance is given: nothing tells the agent when to pick this over 'mandates' (list) or 'record_mandate' (write), nor what a valid id must reference. The reader must infer the selection criteria from the plural sibling names alone.

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