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

There are no annotations, so the description carries the full behavioral burden. It discloses the access requirement (ChainHelix API key or paid payment options), and the output composition (mints, burns, counts, dollars, large events, net). While it does not explicitly state read-only, the data-query framing is clear enough.

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 text is appropriately sized and makes every sentence count, but it is not front-loaded: the access/payment details lead, pushing the actual tool purpose to the second sentence. The core function would be better served if stated first.

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 an analytics query with an output schema present, this is reasonably complete: it covers parameters, defaults, access, and output semantics. It omits response-level detail like pagination or error conditions, but those are lesser gaps given the output schema.

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%, but the description compensates well: 'window in hours' and default/max are given, and 'Omit chain for all' explains the optional behavior of the chain parameter. The parameter values are clear even without additional schema descriptions.

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 that the tool reports stablecoin mints and burns per chain and coin, listing specific outputs (counts, total dollars, large events, net). The resource and action are unmistakable, and the stablecoin focus differentiates it from related siblings like bridge_flows or whale_flows.

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?

It gives operational guidance ('window in hours, default 24, max 720', 'Omit chain for all'), which helps an agent understand how to parameterize a call. However, it does not explicitly mention when to prefer this tool over sibling alternatives or what scenarios are not appropriate.

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