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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds valuable behavioral detail by listing exactly what is verified, including expensive deep checks for recent blocks, and notes there is no cost or authorization barrier.

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?

The description is two compact sentences, front-loaded with the main action and scope. The enumeration of checks is dense but useful, and the closing 'Free; anyone can run it' adds access context without wordiness.

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 read-only verification tool with one optional, fully described parameter and no output schema, the description gives enough context to invoke it correctly. It does not state the return format or failure behavior, but the core verification scope and access model are covered.

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 the deep_last parameter is already documented as controlling re-derivation for recent blocks. The description's phrase 'for recent blocks' reinforces that behavior but does not add syntax, limits, or meaning beyond the schema and parameter description.

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?

The description states a specific verb and resource: verify the whole Quantum Ledger, and enumerates the exact checks performed (SHA3-512 hashes, hash links, both signatures, log roots, entry roots, RFC 9162 proofs). The word 'whole' distinguishes it from sibling tools like qledger_block, qledger_entry_proof, and qledger_status.

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 'whole Quantum Ledger' scope makes clear this is for full-chain verification rather than block or entry-level checks. 'Free; anyone can run it' gives useful access context, but the description does not explicitly name when to prefer siblings such as qledger_block or qledger_status.

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