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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the exact cryptographic pipeline (SHA-256 over the entry, keccak256 up the proof, root compared against the published Passport), the scope limit ('it proves that the record contains the entry; it does not make a statement true'), and determinism with no model involved. It omits auth/prerequisite details, which is minor here.

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 definition is dense but front-loaded: the artifact and its contents come first, the scope caveat and default behavior follow. Sentences are long and clause-heavy, but each carries information that is not duplicated in the schema or annotations.

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 carries the burden of explaining the return value, and it does so well — the proof, the entry, and the steps to verify without trusting RUTHVEN. Combined with 100% schema coverage on inputs, an agent has enough to call it correctly; only the precise response shape and sibling selection remain unstated.

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%, so the schema already documents all three parameters with examples and the maxItems cap. The description only adds the default-behavior case when both optional arrays are absent, which is a behavioral note rather than new parameter semantics. Baseline 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?

The description names a concrete artifact (a Merkle proof over evidence records in the issued Origin Passport) and describes its contents: the entry each record rests on plus the verification steps. That is a specific verb+resource, not a restatement of the title. It never contrasts itself with the sibling ruthven_verify_claim, so sibling differentiation is left to the reader.

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?

It gives one concrete usage rule — with neither evidence_ids nor paths, the call returns the paths that can be proved — which is genuinely useful routing information. However it never says when to use this tool rather than ruthven_verify_claim or ruthven_get_provenance, so the choice among the proof/verification siblings remains implied.

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