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

With zero annotations, the description carries the full disclosure burden and does so reasonably: 'FREE — no payment required' discloses cost behavior and 'public record' implies open access with no auth. The provenance explanation (lock_hash, merkle root, on-chain tx committed before outcome) is a meaningful behavioral trait — the data is verifiable rather than claimed. Minor gaps: no explicit read-only/no-side-effects statement and no failure behavior for invalid token_id.

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?

Four tight sections — purpose, cost note, usage guidance, and args — each earning its place. The purpose is front-loaded in the first sentence, and the verification explanation is dense but directly relevant to calling the tool correctly. No filler, no restatement of schema content.

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-parameter read tool with no output schema and no annotations, the description covers the essentials: what is returned, when to use it, the verification data included, and the parameter range. Gaps are minor — no formal return structure and no error-handling guidance for out-of-range token_id — but an agent can select and invoke this tool correctly from the description alone.

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 0% — the schema only declares token_id as an integer with no description. The description fully compensates: 'token_id: minted soul, 1-273' supplies the real-world meaning and the valid range. This is exactly the semantic value the schema lacks, giving an agent everything needed to supply the argument correctly.

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 the purpose with a specific resource ('ONE Undesirable soul') and enumerates exact contents ('every open (locked) prediction and its recent scored results'). Distinguishes from siblings via scope (single soul vs. souls_in_wallet's multi-soul scope) and the 'FREE — no payment required' note. The retrieval intent is unambiguous even though the verb is implied rather than literally 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?

Provides an explicit 'Use this when:' clause with two concrete scenarios — inspecting a specific soul's calls in detail and verifying a call. Explains why this tool fits verification by describing the on-chain lock_hash, merkle root, and commit transaction that make records checkable. However, it names no alternatives and gives no when-not-to-use guidance, leaving the choice against siblings implicit.

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