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 the full burden. It mentions 'high-resolution intraday data' which hints at detailed data, but fails to disclose critical behavioral traits such as rate limits, data freshness, authentication needs, or what 'OHLCV' specifically entails (e.g., open, high, low, close, volume). This leaves significant gaps for an agent to understand operational constraints.

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 with two short phrases: '5-minute OHLCV price bars. High-resolution intraday data.' Every word earns its place by specifying timeframe, data type, and resolution without any waste or redundancy.

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?

Given the complexity of financial data tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain return values (e.g., structure of OHLCV bars), data sources, latency, or error handling. For a tool with no structured output and behavioral gaps, this is inadequate for an agent to use effectively.

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 clear descriptions for 'token' and 'limit' parameters. The description adds no additional parameter semantics beyond what the schema provides, such as format details for 'token' or constraints on 'limit'. Baseline 3 is appropriate since the schema adequately documents parameters.

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 '5-minute OHLCV price bars' and 'high-resolution intraday data', which specifies the verb (provides/returns) and resource (price bars/data). It distinguishes from siblings like history1d and history1h by specifying the 5-minute timeframe, though it doesn't explicitly name those alternatives.

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 for intraday data analysis by mentioning 'high-resolution intraday data', suggesting it's for short-term timeframes. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like history1h or history1d, nor does it mention any exclusions or prerequisites.

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