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

Beyond the annotations it discloses the full lifecycle (send amountIn before the deadline, output to recipient, refund to refundTo), custody posture ("Funds never pass through us"), and operational constraints (x402 payment at $0.01/call on Base, prepaid x-credit-token header, 1 free call/day, no API key). The one caveat is that "executable swap" and "binding quote" sit in mild tension with readOnlyHint=true/idempotentHint=true, though the non-custodial framing and external deposit step make that defensible rather than a direct contradiction.

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 first clause is well front-loaded and immediately actionable, and most sentences do earn their place (deadline, refund path, safety gate, pricing). However, the body is a dense run-on that mixes execution mechanics, token-safety rules, tracking, and billing without structural separation, which makes it harder to scan than its length warrants.

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?

For a complex, cross-chain, paid, non-custodial swap, the description covers the inputs, the execution/refund lifecycle, the safety precondition, the tracking tool, and the payment model, and an output schema exists so return values need no explanation. The remaining gap is selection guidance against the near_swap_quote sibling and any note on the optional slippage/depositType behavior.

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 schema already documents from, to, amount, recipient, refundTo, slippage, and depositType. The description only restates the required set ("Required inputs: from, to, amount, recipient, refundTo") and adds no format, default, or semantics beyond what the schema provides; slippage and depositType are not mentioned at all. Baseline 3 is appropriate when the schema carries the parameter burden.

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 lead sentence gives a specific verb and resource — "Swap any asset through NEAR Intents — get a deposit address" — and clarifies the artifact returned is a binding quote plus deposit address. It names two siblings (near-token-safety, near-swap-status) for the safety and tracking steps. It stops short of 5 because it never distinguishes itself from the adjacent near_swap_quote or the other swap tools in the sibling list.

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?

It states clear applicability ("Any asset NEAR Intents routes, across chains"), lists the five required inputs, and gives a conditional rule ("Buying a NEAR token runs near-token-safety first and refuses a STOP token unless force=1"). It also routes the agent to near-swap-status for follow-up. It does not, however, state when to prefer near_swap_quote, base_swap, or swap_route instead.

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