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

Goes well beyond the annotations by disclosing that the call spends real money, that price is snapped to the tick schedule (down for back, up for lay) and that the snapped value is what the order executes with, and that request_uuid is what makes a retry after a timeout safe. The idempotency statement is a caller-supplied mechanism rather than a claim that the tool is inherently idempotent, so it complements rather than contradicts idempotentHint=false and destructiveHint=true.

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?

Six sentences, each carrying distinct information, with the destructive warning front-loaded right after the purpose. Dense but purposeful; the only mild cost is that the prerequisite, snapping, and idempotency rules arrive in a fairly packed block.

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?

An output schema exists, so return values need not be described. Given the tool is destructive, open-world, and money-spending, the description supplies exactly the missing context an agent needs: custody of funds, prerequisite betslip, price-snapping semantics, idempotency strategy, and human confirmation.

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 100%, so the baseline is 3. The description adds genuine meaning on top: it explains the snapping behavior that governs what the supplied 'price' actually becomes, and the idempotency role of request_uuid. It does not cover duration, exchange_mode, or the accept_* flags, which is why this is a 4 rather than a 5.

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?

States a specific verb and resource ('Place an order against a betslip') and immediately distinguishes itself from the sibling create_betslip by naming it as a prerequisite. An agent can tell this is the execution step, not the betslip-creation step, without opening either schema.

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?

Gives explicit preconditions ('Requires an existing betslip from create_betslip'), an explicit instruction ('Always pass request_uuid'), a user-facing workflow rule ('Confirm the stake with the user before calling this'), and points to get_order as the follow-up retrieval path. Nothing about when to reach for this tool is left to inference.

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