Daily activity for one asset

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

With no annotations provided, the description carries the full burden. It does disclose meaningful behavioral context: data is aggregated 'per UTC day', volume is in 'raw units', and it distinguishes certain transfer classes. However, it never states the return format, whether the operation is read-only, or how the optional 'days' parameter affects results.

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 sentence with a list, so it is compact and free of filler. However, the phrase 'Transfers as economics' is awkward and cryptic, and the sentence packs many metrics into a dense structure that may reduce readability.

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?

There is no output schema and no annotations, so the description must explain what the agent should expect. It lists output metrics but not the response shape, time series organization, or the effect of the 'days' parameter. This leaves an agent uncertain about how to interpret the result or set parameters correctly.

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 50% (symbol documented, days undocumented). The description adds no explanation for the 'days' parameter and does not tie the 'per UTC day' phrase to the parameter semantics. It only reinforces the symbol's meaning via 'one asset', so it fails to compensate for the undocumented parameter.

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 title 'Daily activity for one asset' clearly identifies the resource and scope, and the description enumerates the specific metrics returned (transfers, volume, mints, burns, USDG-settled transfers, non-US-market-hour transfers). This is a specific and informative description, though it does not explicitly differentiate from siblings like 'history' or 'events'.

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 gives no guidance on when to use this tool versus alternatives. It implies use for retrieving daily asset activity, but there is no mention of exclusions, prerequisites, or how it differs from sibling tools such as 'history' or 'holders'.

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