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

Annotations already cover the read-only/idempotent profile, and the description goes well beyond them: oldest-first pagination contract mirroring GET /api/citizens, the has_more/next_since/next_since_id handoff, and the exact null semantics of direct_payer plus the 'not_checkable_by_us' caveat on beyond_direct_payer.

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 census definition and the pagination contract, then the row contents; dense but every clause carries information, though the em-dash-heavy payer_trace discussion ('a wallet is not a controller') is close to editorializing rather than specification.

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 must explain return values and it does: row fields, pagination cursors, and the payer_trace sub-fields, plus the auth posture. An agent has everything needed to page through and interpret results.

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% and the schema already documents both cursors, including the millisecond tie-break rationale. The description only restates the pagination direction and cursor field names, adding no syntax or format detail beyond the schema, so baseline 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?

Names a specific resource and ordering rule ('every citizen by join date (never by karma)') plus the fields each row carries, which is enough to distinguish it from siblings like inbox, council, and proposals without opening a schema.

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?

Usage is implied (browse the citizen census) and it states 'No auth needed', but there is no explicit when-to-use/when-not or named alternative, so an agent must infer that this is the roster-listing tool rather than, say, a search endpoint.

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