verify_peer_ledger

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

With no annotations, the description carries the full burden and largely succeeds: it discloses zero side effects, no access to the peer's machine, and a three-valued ok result with an explicit warning not to treat null as a pass. It also explains first_break as a line number and nuances declared_breaks. The one flaw is referencing `verified_scope` without defining it, leaving a gap in an otherwise thorough behavioral disclosure.

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 long (~180 words) but dense and front-loaded with the trigger scenario and core operation. Every sentence earns its place given there is no output schema to offload return-value semantics. The dangling reference to `verified_scope` is a minor structural wart, and the 'mark of honesty, not integrity' phrasing is slightly elaborate, but overall the length is justified by the complexity.

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 tool with no annotations and no output schema, the description explains most of the return semantics (ok, first_break, declared_breaks) and side effects. However, `rows` is never described, and the description explicitly instructs the agent to read `verified_scope` without defining it — a real gap for an agent trying to interpret the result. Error behavior for malformed JSONL is also unaddressed, leaving the description mildly incomplete for a complex trust-decision 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 coverage is 100%, so the baseline is 3. The description adds contextual reinforcement (verification operates 'over the text alone') but does not materially enrich the parameters beyond what the schema already says, particularly for strict, which the schema documents fully. No deduction, but no credit beyond baseline.

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, resource, and scenario: decide whether to trust another agent's exported ledger as JSONL text by recomputing its hash chain. The framing ('no access to their machine, no writes on yours') implicitly but clearly distinguishes it from sibling tools like ledger_verify, which operate on one's own ledger, and ledger_append/declare_break, which mutate or annotate it.

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 opening line gives a clear, concrete trigger condition: use this when another agent hands you its exported ledger and you must decide whether to trust it. It does not explicitly name alternatives or state when not to use it (e.g., 'use ledger_verify for your own ledger'), so it stops short of a 5, but the context is unambiguous.

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