needledrop_verify

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool is verification-only, recomputes entry hashes, checks prev_hash linkage and chain head, and fails on tampered or corrupt ledgers. It does not describe the success return/exit behavior, which is a minor gap.

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?

Two dense, front-loaded sentences. Every clause adds operational detail—verification scope, checks performed, failure condition, default path, and parameter guidance—with no filler or repetition.

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 single-optional-parameter tool with no output schema, the description provides enough to invoke it correctly: exact verification checks, tamper/corruption failure behavior, default input, and how to override the default. The only notable omission is what a successful verification returns, but that does not block correct tool selection or invocation.

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 useful details such as 'absolute path' and the default file location, but its stated default (vendor/needledrop/example-ledger.json) is not clearly aligned with the schema's 'canonical CWI needle-drop.json', introducing some ambiguity about what happens with no file argument.

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 opens with 'Verify-only' and states a specific operation: checking hash-chain integrity of a cwi-needledrop/v1 ledger. It names the exact checks performed and explicitly contrasts with signing/sealing, making the tool's purpose unmistakable and distinguishable from the sibling ledger getters and trust_verdict.

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 gives clear usage context: verify a ledger, default to the vendored example, or pass an absolute file path for any other cwi-needledrop/v1 ledger. It does not explicitly name an alternative sibling to use instead, but the 'No signing, no sealing — verification only' note removes the main boundary confusion.

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