Get order book

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

No annotations are provided, so the description carries the burden. It adds useful behavioral context: prices are on-chain CLOB prices, futures require expirationAt, and perps is a single book. However, it does not state that this is a read-only operation or describe response behavior like maxLevels limiting depth, leaving the agent to infer these.

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 two terse, front-loaded sentences with no filler. Every clause earns its place: the core purpose, the futures requirement, and the perps distinction.

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 must cover more ground. It handles venue differentiation and the expirationAt requirement, but it does not explicitly say expirationAt should be omitted for perps, say what maxLevels controls beyond defaults, or indicate the shape of the returned book. Adequate for basic invocation but with clear gaps.

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 only 33%, and the description compensates for the most important parameter by noting expirationAt's unit and conditional requirement. The venue enum and maxLevels constraints are in the schema, but maxLevels is not explained in the description, so coverage remains partial.

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 opens with 'On-chain CLOB prices,' which clearly identifies the resource (order book) and domain (on-chain CLOB), and the title supplies the verb. It distinguishes futures from perps, but does not explicitly differentiate from sibling tools, so it misses the top score.

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 gives concrete usage context: for futures, expirationAt is required; for perps, there is a single perpetual book. This tells the agent how to adjust calls based on venue, though it does not mention any alternatives or explicit when-not-to-use scenarios.

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