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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value by disclosing the hash-chain structure (each digest contains the prior prev_hash) and the returned fields, but says nothing about auth requirements, error behavior, or ordering/pagination limits beyond the cap.

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?

Purpose is front-loaded, followed by parameters, return shape, and an example; every element is useful. It is somewhat dense and repeats schema-documented parameter defaults, which keeps it from a 5.

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 compensates well by enumerating return values (balance, direction, counterparty, amount, digest, prev_hash). It leaves edge cases such as unknown accounts or ledger ordering unaddressed, so it is strong but not exhaustive.

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 coverage is 100%, and the description essentially restates what the schema already documents (account_id identity, limit default 50 / max 200). It adds the worked example, but no new semantics beyond the schema, so the baseline of 3 applies.

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+resource pair: query the settlement account balance and its transaction ledger with hash-chain proofs. It clearly distinguishes itself from settlement.account and settlement.transfer by emphasizing reconciliation and chain verification.

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 clear usage context: multi-Agent settlement reconciliation, checking an Agent's income/expense, and verifying chain integrity. It does not explicitly exclude alternatives or say when to prefer settlement.account instead, so it stops short of a 5.

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