get_crypto_latest_orderbook

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

With no annotations, the description discloses important behavioral traits: the response includes 'full order book depth and can be large'. It also highlights a required parameter value. However, it does not explicitly state that this is a read-only operation or mention rate limits.

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?

Three short sentences each serve a distinct purpose: definition, mandatory parameter, and output size warning. No unnecessary filler or repetition.

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 a simple 2-parameter tool with an output schema present, the description covers the essentials: what it returns, the key parameter constraint, and the large response. The only minor gap is the potential confusion between the enum values and the directive to always use 'us'.

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%, but the description adds value by telling the agent to always set loc to 'us' despite the enum allowing other values. It also confirms that symbols can be a list ('one or more'), matching the comma-separated format.

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 'Returns the latest orderbook for one or more crypto symbols', specifying the verb, resource, and scope. This distinguishes it from sibling tools like get_crypto_latest_trade and get_crypto_latest_quote.

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 clear context for when to use the tool and includes a critical operational instruction ('always set loc to "us"'). It does not explicitly name alternatives or exclusions, but the large response warning helps set expectations.

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