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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful scope context — a fixed 24h window and the metric set — but says nothing about response shape, aggregation guarantees, or behavior for chains with no indexed venues.

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?

One front-loaded sentence with a colon-delimited metric list and zero filler. It is tight, though the fragmented phrasing ('A chain's last 24 hours on the venues Chord indexes') is slightly elliptical and could read more naturally without gaining length.

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?

With no output schema, the description correctly carries the burden of stating what is returned, which it does via the metric enumeration. For a one-parameter read-only tool with complete annotations and full schema coverage, this is nearly sufficient; only the response shape and empty-chain behavior remain unstated.

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 100% and the single enum parameter is documented in the schema, including a pointer to chord_chains for supported keys. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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 names the resource (a chain), the fixed time window (last 24 hours), the data source (venues Chord indexes), and enumerates the returned metrics (volume, swaps, venue share, hourly buckets). This is specific enough for an agent to know it is a chain-level 24h aggregate, though it does not explicitly contrast itself with siblings like chord_candles or chord_trades.

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 explicit when-to-use, when-not-to-use, or named alternative; the agent must infer from the metric list that this is the high-level summary tool. The mention of 'venues Chord indexes' hints at coverage but gives no routing guidance among the 17 sibling tools.

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