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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context about the granularity (per-token and total) and the fact that it reports swap volume, but it does not disclose additional behavioral details such as result structure, ordering, pagination, or any rate-limit/auth expectations.

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?

The description is a single compact sentence that front-loads the core purpose and enumerates the window options in parentheses. There is no redundant text, no filler, and it is immediately scannable by an agent.

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?

For a simple read-only metric tool with one optional parameter and no output schema, the description gives enough context to select and call it: it states the output type (swap volume), the aggregation granularity (per-token and total), and the available windows. A more detailed explanation of return values or default behavior would improve completeness, but the description is largely sufficient given the tool's low complexity.

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 schema already provides a full description of the single 'window' parameter, including its allowed values and default. The tool description essentially repeats this same information without adding any new semantic meaning, so it adds no value beyond the schema and merits the baseline score.

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 clearly states the tool's function: reporting per-token and total swap volume over a selectable time window. It communicates the resource (swap volume) and the main variants (1h, 24h, 7d, 30d, all), but it does not explicitly differentiate itself from sibling tools such as recent_swaps or market_stats, and it lacks an explicit verb like 'get' or 'fetch'.

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 description implies when to use the tool: whenever per-token or total swap volume for a given window is needed. However, it provides no explicit guidance about when not to use it or which alternative sibling tool should be preferred for related but different data, leaving some ambiguity for tool selection.

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