HIP-4 Daily Volume

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 adds genuinely useful behavior the schema cannot express: HIP-4 fills are indexed from mainnet launch 2026-05-02 and the API clamps every look-back to that date. It stops short of describing response shape or truncation behavior, which matters since there is no output schema.

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?

Two sentences, front-loaded with the payload contents before the usage cue and the data-coverage caveat. Every clause carries information an agent needs; nothing is restated from the name or title.

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 read-only, no-output-schema tool the description compensates well by naming the returned metrics and warning about the launch-date clamp. The only remaining gap is expected response structure/pagination, which is minor given the annotations and the small 2-parameter surface.

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 coverage is 100% and both parameters are fully documented in the schema (days default/max, useToonFormat default). The description adds only 'by day' granularity and does not elaborate on the 1–60 day clamp or the toon-format toggle, so the baseline 3 is appropriate.

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 and resource ('Get daily HIP-4 volume trajectory') and enumerates the exact measures returned: fills, unique trades, unique wallets, contracts, notional USDH by day. That granularity separates it from siblings such as hip4_andwer_summary or hip4_most_active without the agent needing to open any schema.

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?

'Use for outcome-market activity trends' gives a clear usage context, and the pointer to data_coverage for freshness is a useful secondary route. However, it never names an explicit alternative (e.g., hip4_outcome_summary, hip4_most_active) or a when-not condition, so routing remains partly inferential.

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