analytics / volume_fees

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description's one added fact — that indexed coverage may be partial — is genuinely useful caveat context, but it says nothing about aggregation window behavior, pagination, or how gaps manifest.

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 with no filler; the coverage caveat is placed where it will be read. It is efficient, though arguably too sparse for a tool with three undocumented parameters.

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?

No output schema and 0% parameter documentation mean the description carries the full burden, and it does not: return shape, aggregation granularity, and parameter behavior are all unstated. Only the partial-coverage warning is provided.

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 0% across three parameters, and the description supplies no meaning for chain_id (required), pool, or since_timestamp. Without any hint on units, timestamp semantics, or whether pool is optional scoping, an agent must guess.

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 verb ('Aggregate') and a resource ('indexed swap input and fee amounts in raw token units'), so the general intent is graspable. But it never clarifies whether the result is a total, a time series, or per-pool breakdown, and it draws no line against siblings like analytics.turnover or analytics.tvl, leaving overlap ambiguous.

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 prerequisites, and no named alternative among the many analytics.* siblings. 'Never presume complete coverage' is a caution about results, not a routing hint about when this tool is the right choice.

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