get_orderbook

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

No annotations are provided, so the description carries the burden. It mentions the tool fetches bids and asks and requires no API keys, but does not disclose response format, pagination, or behavior for invalid symbols. This leaves some ambiguity.

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?

Two concise sentences with no extraneous information. Every sentence adds value: first states the function, second adds a key behavioral note (no API keys needed).

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 output schema, the description provides essential context: it returns bids and asks for a symbol on an exchange. It could mention the structure of bids/asks (e.g., price and size), but the current description is mostly complete for a simple query tool.

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 coverage is 100% with descriptions for both parameters. The description adds only 'Works without API keys' and implies the exchange list from the schema. This meets the baseline but does not significantly enhance understanding beyond the schema.

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 retrieves the order book (bids and asks) for a symbol on an exchange, with the specific verb 'Get' and resource 'order book'. It distinguishes itself from sibling tools like get_prices or get_markets by specifying depth-related data.

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 notes it 'works without API keys', which implies usage without authentication. However, it does not explicitly state when to use this tool versus alternatives like get_prices or get_markets, but the purpose is clear enough from context.

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