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

No annotations are provided, so the description carries the full burden. It signals a read-only analytics operation and a 'real-time' freshness claim, which is useful, but it says nothing about rate limits, latency, coverage gaps per chain, or what happens when a ticker is ambiguous across chains.

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 dense sentences that front-load the domain and then enumerate the analytic outputs. No filler, though the trailing metric list reads as keyword stuffing rather than agent guidance.

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 and no annotations, the description does most of the work by enumerating the returned metrics (pressure, liquidity, velocity, FDV, pools). It stops short of stating response shape or chain-coverage caveats, but an agent has enough to call it 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 100%, so both parameters are already documented in the schema (query with ticker/address examples, chain enum with default). The description's 'any token ticker or contract address' merely restates the query param and adds nothing about the chain 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?

Names a specific capability set (order-flow analysis: buy/sell pressure, liquidity depth, volume velocity, FDV, top DEX pools) and the input domain (token ticker or contract address). An agent can tell this apart from analytics-only siblings like defi_yields, though no sibling is explicitly named.

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 alternative routing. The description only implies usage ('for any token ticker'), leaving the agent to guess how this differs from defi_yields or wallet_profiler when the question is token-level vs. protocol-level.

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