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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds output-shape context (an ordered checklist of quote, fund, re-quote) and asset constraints (native USDC not USDC.e, ETH needed for gas), which is useful. The cryptic 'Offline.' is never explained, so behavioral disclosure is only moderate.

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 sentence is dense and largely front-loaded around the funding requirement, but the leading 'Offline.' is a wasted, unexplained fragment and 'requoteOf' is internal jargon. It is short overall, but not every token earns its place.

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, return values need not be spelled out, yet the description usefully sketches the checklist. Gaps remain: the 'detail' parameter is unexplained, the 'Offline.' claim is unclarified, and the tool's relationship to the quote/swap siblings is left to inference. Adequate but with clear gaps for a 4-parameter 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 75%, so the schema carries most parameter meaning, and the direction descriptions in the schema mirror the description's u2x/x2u text. The description adds the compound input form 'from {chain, asset} (and amount)' but says nothing about the 'detail' (lean/full) parameter, leaving one parameter unexplained beyond the schema. Baseline 3 is appropriate.

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 the resource (funding instructions for a swap) and distinguishes the two funding paths (native USDC + ETH for gas on Arbitrum One for u2x vs. XMR for x2u). It never states the verb plainly ('returns how to fund'), and the opening 'Offline.' is opaque, but an agent can still grasp what the tool produces. Sibling differentiation from get_quote/plan_swap is implied via the quote/fund/re-quote ordering rather than stated.

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?

'Pass from {chain, asset} (and amount) for one ordered checklist' gives invocation guidance for the input, and the u2x/x2u framing implies when each direction applies. However, it never says when to call this vs. get_quote, plan_swap, or create_swap, and no prerequisites or exclusions are given. Usage is implied rather than stated.

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