verify_evidence_ledger

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

With no annotations, the description carries the full behavioral burden. It usefully discloses a key limitation (it cannot detect whole-ledger replacement), which is genuinely valuable scope information, but it omits what checks are performed, whether the operation is read-only, and what a pass/fail result looks like.

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?

A single clause states the action first, then the critical scope limitation, with zero filler. Every word earns its place and the most decision-relevant caveat is front-loaded after the core purpose.

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 tool with no annotations and no output schema, the description covers purpose and one limitation but does not describe the return value or what 'integrity' encompasses. Adequate but leaves an agent guessing at the outcome semantics of a verification call.

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 takes zero parameters, so per the baseline this scores 4. There are no input semantics for the description to clarify, and the empty schema is consistent with the description's self-contained verification scope.

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 ('Check local JSONL ledger integrity'), and the 'ledger' resource clearly differentiates it from sibling verify_* tools like verify_citation and verify_claim. However it never names or contrasts with any sibling explicitly, so the differentiation is inferred from the unique resource rather than stated.

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 description implies its usage context (verifying a local ledger's integrity) but gives no explicit when-to-use trigger and names no alternative tools. The 'cannot detect replacement of the entire ledger' clause is a scope caveat rather than routing guidance, so an agent has only an implicit sense of when to prefer this over other verification tools.

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