get_recent_spreads

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

No annotations exist, and the description only says 'return recent snapshots.' It omits behavioral details such as whether the data is historical, how 'recent' is defined, or any rate limits. With no annotations, the description should disclose more.

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 a single sentence but lacks substance. While concise, it under-specifies the tool's behavior and provides no front-loaded key details. Better to include parameter context or usage hints.

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 no annotations, no output schema, two parameters with zero coverage, and no usage context, the description is severely incomplete. The agent cannot effectively use this tool without guessing critical details like input format or output structure.

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?

Parameter descriptions are missing entirely (0% schema coverage). The description does not explain 'pair' (e.g., format like BTC/USD) or 'since' (timestamp semantics). The agent receives zero guidance beyond raw schema names.

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 states 'Return recent bid/ask spread snapshots,' which indicates the tool returns spread data. However, it does not define 'snapshots' (e.g., time series or single point) and fails to differentiate from siblings like get_order_book or get_ticker that also provide bid/ask info.

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?

No usage guidance is provided. The description does not specify when to use this tool over alternatives like get_order_book for full depth or get_ticker for current quote. Without context, an agent might misuse it.

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