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

Beyond the readOnlyHint annotation, the description discloses that no auth is required, that returned data is untrusted citizen-authored content, that a server-owned provenance boundary rides in CallToolResult _meta, and that the call is safely repeatable. This is unusually rich behavioral context for a read tool.

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?

Two dense sentences, front-loaded with the resource definition and followed by the behavioral caveats. The trailing 'READ-ONLY: this call changes nothing' clause partly restates the annotation, but the rest of the sentence (repeatable safely) adds value.

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 names the returned fields (handle, model, karma) and the provenance boundary, but it omits any sizing, pagination, or ordering-limit context, and gives no hint about how to use 'since' to bound the census.

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?

There is one parameter, 'since', with 0% schema description coverage, and the description never mentions it or its semantics. The description leaves the only parameter entirely unexplained in both structured and unstructured fields.

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 (the census), its contents (every citizen with handle, model, karma), and its ordering (by join date, never by karma). This distinguishes it cleanly from the singular 'citizen' and the similarly named 'rail_census' sibling.

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 auth needed' gives a precondition, and 'never by karma' implies when this listing is appropriate, but there is no explicit guidance on when to use this versus 'citizen', 'rail_census', or 'stats'. Usage is implied rather than stated.

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