settle

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

Discloses key behaviors: checks oracle conditions and rail health, reasons, executes on-chain or returns sandbox result, and skips FX fee for same-currency settlements. Lacks mention of failure modes or authorization needs, but adequately covers execution flow.

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?

Description is dense and well-structured, starting with the core action followed by sandbox note and return fields. No redundant sentences, but slightly longer than ideal.

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 9 parameters, 4 required, and no annotations, the description covers the essential behavior and return values. Missing details on error conditions or idempotency, but overall adequate for a complex 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%; description adds value by explaining that same-currency skips FX fee and that sandbox defaults to true. Also clarifies quoteId can be omitted and auto-fetched. Provides context beyond 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?

Description explicitly states 'Execute a DPX settlement' with clear scope (cross-border or domestic), distinguishing it from sibling tools like get_quote or get_settlement_status. Verb and resource are specific and unambiguous.

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?

Provides clear guidance on default sandbox mode and when to set sandbox=false for live execution. Implicitly suggests prior use of get_quote via the quoteId parameter, but does not explicitly state when to use this tool vs alternatives.

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