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

With no annotations, the description carries the full disclosure burden and delivers little: 'feed' and 'real-time' hint at streaming behavior but the return shape is never stated, nor whether results are snapshots or continuous, which exchanges are covered, what authentication or rate limits apply, or whether arbitrage opportunities are pre-computed or raw depth. For an unpaginated, unspecified market-data tool this leaves the agent guessing about cost and output.

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?

A single compact sentence that front-loads the tool name and then lists the covered data domains; there is no padding or redundancy. Its brevity is efficient rather than verbose, though it comes at the cost of underspecification addressed in other dimensions.

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?

No output schema and no annotations exist, so the description is the only place an agent could learn what comes back, what exchanges or pairs are supported, or whether arbitrage scores are computed. Given the multi-domain scope implied by the name and a parameter that limits 'structured items,' the definition does not say what an item is — a significant gap.

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?

There is a single optional integer parameter (maxResults) with 100% schema description coverage, so the schema already explains it adequately. The description adds no meaning beyond the schema, but with one fully documented parameter the baseline of 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 data domains it covers (cross-exchange orderbook depth, spread arbitrage, liquidity imbalance) but is phrased as a title restatement with no verb describing what the tool actually does — scan, return, stream, or compute. An agent knows the subject matter but not the action, and nothing distinguishes it from crypto-adjacent siblings like dex_token_scanner_security_auditor.

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?

No when-to-use guidance, no exclusions, and no named alternatives are given. The only usage signal is the word 'real-time,' which does not tell an agent when this tool is the right pick over other crypto or scanner tools in the catalog.

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