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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the bar is lower; the description still adds real value by disclosing data provenance – curve fees measured on-chain versus pool fees computed from volume – which tells the agent the two figures have different reliability characteristics. It does not mention freshness/caching or latency, which is the only notable gap.

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?

A single front-loaded sentence that opens with the core purpose and then enumerates the payload, followed by one short line on methodology. Dense but every clause carries information; nothing is redundant with the title 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 carries the burden of describing return content and does so thoroughly by listing every section an agent will get. Missing only minor operational detail such as response shape or whether claimable amounts are wallet-specific versus global.

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%, so the schema already documents both 'top' (count, highest first) and 'sort' (ranking key). The description only alludes to ranking via 'the top coins' and adds no meaning about sort modes or how the top-N list interacts with the totals; 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+resource ('Every fee higher.fun's coins have paid and who got it') and enumerates the breakdowns returned (creators, higher.fun, Raydium, pools, phase, fee mode, claimable, rates, top coins). It is clearly an ecosystem-wide aggregate, which implicitly separates it from the per-coin sibling get_coin_fees, but it never names that sibling explicitly.

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?

Usage is implied rather than prescribed: 'The same numbers as highwire.fun/fees' tells an agent which view this mirrors, and the scope framing implies it is the aggregate counterpart to get_coin_fees. There is no explicit when-to-use/when-not-to-use guidance or reference to a named alternative.

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