x402 crypto market structure

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'bundle' and 'combined' but doesn't specify whether this is a read-only operation, what data format is returned, whether there are rate limits, authentication requirements, or any side effects. For a data retrieval tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 just two short phrases. It's front-loaded with the core purpose. While efficient, it might be too brief given the lack of annotations and behavioral context needed for a comprehensive data tool.

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 this is a market data tool with no annotations, no output schema, and siblings that provide similar functionality, the description is insufficient. It doesn't explain what 'combined' means operationally, what data format to expect, or how this differs from using marketSnapshot and marketOrderflow separately. For a tool positioned as 'most comprehensive view,' more context is needed.

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' well-documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides. According to guidelines, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 'Full market data bundle: snapshot + orderflow combined' which specifies the verb (provides) and resource (market data bundle). It distinguishes from siblings by mentioning 'snapshot + orderflow combined' which differentiates it from marketSnapshot and marketOrderflow. However, it doesn't explicitly state what 'combined' means operationally.

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 context with 'Most comprehensive view' suggesting this should be used when needing complete market data. However, it doesn't explicitly state when to use this versus marketSnapshot or marketOrderflow, nor does it provide any exclusion criteria or prerequisites. The guidance is implied rather than explicit.

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