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

With no annotations, the description carries the full behavioral burden and does so richly: it is recomputed on read and cannot go stale, allLanded semantics are explained ('not found' never counts as success), no partial figure is served if the ledger or chain cannot be read in full, signatures are omitted, and it is read-only.

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?

Front-loads what the tool does and then layers semantics (allLanded, the no-partial-figure guarantee, signature omission). Dense and largely waste-free, though it runs long and some clauses could be tightened.

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-param read-only integrity check with no output schema and no annotations, the description covers everything an agent needs: the outcome categories, the allLanded contract, the failure behavior, and why no signature list is returned.

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?

There are zero parameters, so the schema has nothing to document and the baseline is 4. The description correctly does not invent parameter semantics.

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: it looks up every recorded holder payout on Solana and tallies them into confirmed, rejected, or missing. This distinguishes it from siblings like verify_claim and verify_day, which check individual claims or days rather than the whole ledger's agreement with the chain.

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?

Gives a clear purpose-driven context: 'Use it to check that the claim ledger matches the chain rather than trusting it.' However, it does not explicitly name alternatives (e.g., verify_claim) or state when-not to use it, leaving some routing to inference.

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