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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint), and the description is consistent with them, so no bar adjustment caused. It adds genuinely useful context: receipts arrive in three distinct states (observed, confirmed, finalized) and prepared/unsubmitted actions are filtered out, which tells an agent it is not seeing the pipeline of pending work.

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 sentences, no filler: the first fronts the verb, resource, and state scope; the second adds one high-value exclusion. Every word earns its place, and nothing paraphrases the title or annotations.

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?

For a zero-parameter, read-only tool with an output schema and rich annotations, the description is nearly complete: it says what is read, in what states, and what is excluded. The only real gap is the unstated relationship to the similarly named get_census_status sibling, which an agent may need to disambiguate.

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?

The tool has no parameters, so the 4-baseline applies and there is no semantic burden on the description. Nothing about parameters is missing because nothing needs to be said.

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?

Identifies a specific verb and resource: read chain-backed Census receipts plus their observed/confirmed/finalized state. The statement that prepared actions are excluded clearly distinguishes it from the many prepare_* sibling tools, though it never names its closest comparison, so it stops short of full sibling differentiation.

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?

The exclusion line ('Prepared actions are excluded') gives implied guidance about what this tool is not for and hints that prepare_census_receipt is the path for pending work. However, there is no explicit when-to-use statement, no named alternative tool to route to, and no guidance versus the similarly named get_census_status sibling.

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