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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful behavioral context by stating the analysis is 'live', scoped to 'the last hour', and limited to DEX trade flow plus a computed verdict. No contradiction with annotations exists.

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, well-front-loaded sentence: the action comes first, followed by the temporal scope and a compact list of expected outputs. There is no filler or redundant information beyond useful clarification.

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, so the description wisely enumerates the expected return fields: buy/sell volume, buy pressure, price change, largest trade, trader concentration, and verdict. Combined with the chain guidance and read-only annotations, this gives an agent enough context to invoke the tool correctly, though error behavior and edge cases are not addressed.

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?

With only 50% schema description coverage, the prose compensates by explaining the chain choices ('Base by default; also arbitrum, optimism') and clarifying that address is an ERC-20 token contract address. This adds meaning beyond the raw schema, though part of it is redundant with the schema's enum and default.

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 identifies the action ('send a token contract address'), the resource ('ERC-20 token'), and the exact output ('live DEX trade flow' with specified metrics and a 'verdict'). This distinctively separates it from sibling analysis tools like check_token_risk or get_symbol_intelligence, even without naming them.

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 implies usage: use this tool when you need live DEX trade-flow metrics for an ERC-20 token over the last hour. However, it does not explicitly state when to prefer this over alternative tools or mention any exclusions, so the when-to-use guidance is only implied.

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