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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds context beyond that: the operation needs no proof, an empty result is allowed, output is the published value and must be quoted as-is. It does not mention auth behavior of the optional credential parameters or rate limits, hence a 4 rather than a 5.

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-loads what is read and where from, then when to use it, then sibling routing, then the behavioral note. Every sentence carries distinct information with no repetition or 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?

An output schema exists, so return shapes need not be described, and annotations carry the safety profile. The description supplies the remaining essentials: purpose, when-to-use, sibling disambiguation, and the no-proof/empty-allowed behavior, leaving no gap for either selection or invocation.

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 description coverage is 100%, so all four parameters (nonce, leave_token, controller_signature, controller_public_key) are already fully documented in the schema, making 3 the baseline. The description's 'no proof' note usefully signals that these credential parameters are optional and unnecessary for a plain read, but adds no syntax or format detail beyond the schema.

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 verb (Reads) and resource (the published census) plus the exact sources (/city.json and /beacon.json) and the fields it returns (occupancy, hotel guests, citizens). It explicitly distinguishes itself from the sibling tools hotel and pulse by naming which data each covers.

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?

Gives an explicit trigger ('Use it before you state any number about GRITH, and quote it as published') and names two alternatives with the conditions that select them: use hotel for the hotel rail with your own bed, and pulse for the house/outside split and arrival counts. Nothing is left to inference.

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