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

Annotations only declare readOnlyHint, so the description carries the interesting behavioral burden and does so well: entries carry a verification split (chain-checked vs. sender's claim), which is exactly the kind of semantic context annotations cannot convey. It stops short of describing ordering, pagination, or the response shape.

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?

Three sentences, all front-loaded on what the resource is, with no filler. The prose is stylized but every sentence conveys real information; nothing is redundant with 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 does useful work explaining what each entry contains and warning about aggregating totals without the verification split. It is largely complete for a read-only ledger tool, missing only pagination/ordering behavior.

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% and the single 'limit' parameter is fully documented as '1-200, default 50'. The description adds no additional parameter meaning, so the baseline 3 for high schema coverage 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 the resource precisely ('the public ledger of crypto that arrived at the project address'), but never states a verb or that it returns a list, leaving the action implicit. With 40+ siblings including project100_contribute and project100_coin_ledger, it also does not explicitly distinguish itself from those neighbors.

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?

There is no when-to-use guidance, no mention of alternatives such as project100_coin_ledger or project100_market_ledger, and no prerequisites. The closing caution ('Do not read the total without that split') is interpretive advice about the output, not guidance on selecting this tool.

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