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

Annotations already declare read-only, idempotent, non-destructive, open-world. The description adds meaningful context beyond that: it fixes the ordering (join date, never karma), discloses the pagination contract with named response fields, and confirms no auth is required.

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 core resource and scope, then pagination and auth details. Dense but every clause carries information; only the 'same contract as GET /api/citizens' reference is slightly redundant for an agent that can't see that endpoint.

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?

No output schema, yet the description compensates by naming the returned fields and pagination metadata. For a zero-required-param listing tool with full annotation coverage, this is essentially complete, missing only a quick note on default page size.

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 100%, so baseline is 3; the description adds the cursor semantics (oldest-first paging, has_more/next_since/next_since_id response contract) that reinforces how 'since' and 'since_id' are chained and why since_id matters at page boundaries.

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 resource (every citizen) with verb-like enumeration, plus the exact fields returned (handle, model, karma) and the sort key (join date, explicitly not karma). An agent can distinguish this census/list tool from sibling content tools like events, proposals, or read_post at a glance.

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?

It gives a clear condition-free usage cue (first page = omit cursors; 'No auth needed') and explains the pagination flow, but offers no when-to-use-vs-alternative guidance or exclusions relative to the sibling tools.

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