get_order_book

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

With no annotations, the description must disclose safety and behavior. It states it 'shows current buy and sell offers,' implying a read-only operation, but it does not detail response format, pagination, default limit, or how issuers are handled for non-XRP currencies. Minimal behavioral disclosure, though it does convey the core read intent.

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 sentences: the first states the action precisely, the second adds a key detail about contents. No filler or redundancy, and the most important information is front-loaded.

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?

There is no output schema, so the description should convey return values and edge cases. It only gives a high-level statement about buy and sell offers, omitting response structure, default limits, network selection, and the distinction between XRP and issued currencies. For a moderately complex tool with six parameters, this is insufficient.

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?

All six parameters have descriptions in the schema (100% coverage), so the baseline is 3 as the description need not re-explain them. The description adds no further meaning about parameter semantics, such as relationships between base/quote or default behaviors, but neither is required given the schema completeness.

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 identifies the operation ('Get'), the resource ('order book for a currency pair'), and the specific domain ('XRPL DEX'), and adds that it shows current buy and sell offers. This distinguishes it from sibling tools like get_account_info or get_ledger, which target different 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 implies usage for current market data on the XRPL DEX, but it does not explicitly state when to prefer this tool over alternatives, nor note any exclusions or prerequisites. The sibling tool list is provided externally, but the description itself offers no comparative guidance.

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