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: it declares 'Read-only' and clarifies subtle metric semantics (holdersCount/$VAULT vs protocolHoldersTracked/all-projects, activeLocks vs uniqueLockers non-interchangeability). This is genuinely useful beyond a bare read hint, though it omits any freshness/caching or rate-limit context.

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-loaded with the resource name and then builds field-level disambiguation. Dense but every clause (holders vs protocol holders, lock contracts vs lockers) earns its place, and the 'Read-only' tag closes cleanly.

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 and no annotations, the description must explain returns itself, and it does so thoroughly – effectively serving as a prose output schema. It is nearly complete for a no-arg read tool, missing only freshness/pagination context.

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?

The tool takes zero parameters, so there is no parameter meaning to convey; baseline for a no-param tool is 4. The description appropriately spends its words on return-field semantics instead.

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+resource ('Live treasury statistics') and enumerates exactly what it returns (per-asset balances/USD values, vault value, holder payouts, fee totals). The 'Live' qualifier implicitly separates it from the sibling get_treasury_history, but no sibling is named explicitly, so it falls short of a 5.

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 statement of when to use this tool versus alternatives such as get_project_treasury or get_treasury_history. The contrast with history is only implied by the word 'Live', leaving selection guidance to inference.

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