x402 crypto market structure

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

No annotations are provided, so the description carries full burden. It mentions 'real-time' data but doesn't disclose behavioral traits like rate limits, authentication requirements, data freshness guarantees, or whether this is a read-only operation. For a real-time data tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 extremely concise - a single sentence that efficiently communicates the core functionality. Every word earns its place by specifying the data type, key metrics, and scope. There's no wasted verbiage or unnecessary elaboration.

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?

For a real-time data tool with no annotations and no output schema, the description is insufficient. It doesn't explain what format the data returns, how frequently it updates, whether there are subscription requirements, or what 'across exchanges' means operationally. The description leaves too many practical questions unanswered for effective tool invocation.

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%, with the single parameter 'token' clearly documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides (it doesn't explain token format constraints or default behavior). With high schema coverage, the baseline score of 3 is appropriate.

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 states the tool provides 'real-time orderflow data' with specific metrics (buy/sell pressure, delta, imbalance) across exchanges. It uses a specific verb ('provides' implied) and resource (orderflow data), but doesn't explicitly distinguish from sibling tools like marketAnalyze or marketSnapshot, which might offer different market data.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or compare it to sibling tools like marketAnalyze or marketSnapshot that might offer different types of market data. The agent must infer usage from the name and description alone.

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