Crypto recent trades (OKX)

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

Annotations already declare safe read-only, idempotent behavior. Description adds that it returns fields like price, size, side, trade id, timestamp, but does not disclose potential limits on data freshness, ordering, or pagination. Adds some value beyond annotations.

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?

Extremely concise: one sentence outlining purpose, supported by a concrete example. No extraneous information, front-loaded with key details.

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 tool's simplicity (2 parameters, no output schema), the description is largely sufficient. Lists return fields and example usage. Could mention data freshness, ordering (most recent?), or maximum return count, but overall adequate.

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 covers 50% of parameters (instId described, limit not described in schema). Description provides an example usage demonstrating both parameters, which adds practical context but does not fully explain limit's meaning (e.g., maximum number of trades). Partially compensates for gap.

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?

Clearly states it retrieves most recent public trades for an instrument, specifying return fields and compatible instrument types (spot and swap). Distinguishes from sibling tools like crypto_candles which serve different purposes.

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?

Provides clear context for when to use (details recent trades for spot and swap instruments) but does not explicitly exclude alternative tools or provide when-not guidance.

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