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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value on top by disclosing the $500 threshold, the descending-value ordering, the returned fields, and the upstream data provider. The only gap is that it doesn't say how the "links" behave or whether results are cached, which is minor for a read-only list.

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 sentences, front-loaded with the resource, filter, and ordering before the secondary routing hint and attribution. Every clause carries information; the only slight dip is the attribution tail, which aids trust but isn't strictly needed to invoke the tool.

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?

There is no output schema, and the description compensates by enumerating the return shape (total USD value, 24h change, category, top tokens, main chain), which is exactly what an agent needs to decide whether this tool answers the question. Missing only pagination-total behavior and the meaning of the embedded links.

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%, with all three parameters documented (limit range, offset semantics, project slug), so the schema carries the load. The description adds no parameter-level detail such as how project slug interacts with the $500 threshold or whether paging is stable across requests, so 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?

States a specific verb and resource ("Lists DAO treasuries") plus a hard filter (>$500) and sort order (largest first), which an agent can act on directly. It gestures at the sibling distinction via "Use the links for a DAO's daily history" but never names dao_treasury_history or dao_treasury, so the differentiation from siblings is implied rather than explicit.

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 clause "Use the links for a DAO's daily history" points an agent toward per-DAO history rather than this aggregate list, which is a real routing hint. However, it never names the alternative tool and gives no exclusion for when to prefer dao_treasury or dao_holdings_history, leaving the agent to infer the boundary.

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