Estimate a Ripio Trade order

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

The description explicitly says 'Read-only: nothing is executed,' which reinforces the readOnlyHint=true and destructiveHint=false annotations. It also adds useful context beyond annotations by clarifying that this is a real-time estimate, not an execution, and by listing the returned components.

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 well-structured sentence followed by a clear read-only warning. It front-loads the core purpose and output details without wasting words.

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?

With an output schema present and annotations covering safety, the description provides the essential context: what is estimated, what the result contains, and that no order is executed. The three required parameters are sufficiently documented in the schema, so nothing critical is missing for an agent to invoke the tool correctly.

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 description coverage is 67%, with pair and amount already described in the schema. The description adds the market-order context and the notion of 'size,' but it does not meaningfully explain the side parameter beyond the schema's enum, and it adds little over the existing parameter descriptions.

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 names a specific verb ('Estimates'), a specific resource ('a market order on Ripio Trade'), and the key outputs ('unit price', 'gross value', 'taker fee', 'total'). This clearly distinguishes it from sibling tools like ripio_get_prices or ripio_list_open_orders.

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 when to use it — when you need to know what a market order would cost or return before executing — but it does not explicitly state when to prefer it over alternatives like ripio_get_prices or ripio_get_limits. No exclusions or when-not-to-use guidance is provided.

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