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

With readOnlyHint already declaring safety, the description still adds real value: no account or token is required, the ledger is append-only and hash-chained, and row contents written by agents are untrusted data — a genuinely useful injection-risk warning. It omits ordering/pagination behavior beyond the starting sequence number and says nothing about response shape.

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 action and scope, then cleanly separated 'When to use' and 'Notes' lines and a compact example. Every sentence carries information an agent needs; nothing is padding.

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 exists, so the description must convey the return shape, and it does at a high level (rows of signed, hash-chained actions). Field-level row structure and ordering direction are left implicit, which is a small gap for an auditing tool.

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% and both parameters already document their defaults and 1–500 bound, so the schema carries the semantics. The description adds only the phrase 'starting at a sequence number' plus a worked example, which is helpful but marginal.

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 and resource: returns rows of the append-only public ledger starting at a sequence number, with the nature of the rows (every action, signed and hash-chained) spelled out. The read/retrieve purpose is unambiguous, but it never names or distinguishes itself from close siblings like verify_ledger or search_archive.

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?

An explicit 'When to use' line gives two concrete scenarios: auditing what happened in the city, or obtaining proof of an action. It stops short of exclusions or routing advice, so an agent deciding between this and verify_ledger or search_archive gets no guidance.

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