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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the 24-hour window cap, but that constraint is also in the schema, and it says nothing about aggregation behavior, caching, rate limits, or what happens when the window has no data.

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 purpose is front-loaded in the first sentence and the usage caveat follows immediately. The trailing parameter list duplicates the schema and is the only mildly wasteful element, but overall it is tight and skimmable.

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 an output schema present the return shape needn't be described, and the annotations carry the safety profile. Purpose, usage boundary, and parameter enumeration are all present; only the aggregation semantics (e.g. how the window is computed, empty-window behavior) are absent.

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%, so every parameter is already documented with types, defaults, and bounds. The description's parameter block (blockchain options, wallet_type values, hours cap, mint restriction) largely restates the schema without adding new semantics, 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 states concretely what is returned — trade count, value moved, and distinct wallet count over a bounded window — which is more informative than the bare name 'get_activity_metrics'. It also implicitly distinguishes itself from the per-trade sibling by saying it is not for 'the individual trades.' It stops short of a crisp verb+resource statement, but an agent can tell what this produces.

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?

Explicit guidance: 'Use for how busy the market or a single token is, rather than for the individual trades' gives both the appropriate context and an exclusion that routes the agent away from a trade-listing tool. It does not name the alternative tool (e.g. get_recent_trades) outright, so the routing relies on inference.

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