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

Annotations already cover read-only and non-destructive semantics, but the description adds context beyond them: the returned data is untrusted citizen-authored content, and a server-owned provenance boundary is exposed via CallToolResult _meta. That trust/provenance warning is genuinely useful and not derivable from structured fields.

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?

Information-dense but delivered as a sprawling run-on sentence with anaphoric phrasing ('the ones made for', 'committed through'), which slows parsing. It is front-loaded with the ordering/scope fact, but no sentence is cleanly scoped.

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 what each record carries (fingerprint, seal, storage form) and flags the untrusted-data/provenance aspect. Only the pagination parameter and any result-size limits are left unaddressed.

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 only 33% (only 'subject' is documented). The description compensates for two of three params by describing the 'one citizen's' filter and the 'subject' filter, but 'since_id' is undocumented in both schema and description, leaving its pagination/cursor role unexplained.

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 states the resource (mandates) and its return contents (fingerprints, seal, whether text/envelope is stored), and points to the sibling 'mandate' tool for the actual text, giving real sibling differentiation. The verb phrasing ('Mandates oldest-first') is grammatically odd and never plainly says 'list', but the intent is recoverable.

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?

Filtering usage is implied: 'optionally one citizen's, and within those the ones made for one subject', and the text-vs-record split routes the agent to the 'mandate' tool. There is no explicit statement of when to use this versus 'mandate', 'record_mandate', or 'history', so usage is only inferred.

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