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

Annotations already declare readOnly/destructive/openWorld, so safety is covered. Beyond that, the description discloses meaningful behavior: values are 'read at one Wanchain block' (snapshot semantics), it returns the desk's quote/rate/balance and 'whether it can pay,' and it surfaces exact approve and sell calls without recommending a route. It does not mention pagination or refresh behavior, keeping it below a 5.

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?

Front-loaded with the core action, and the trailing skill reference is a useful routing cue. However, the opening sentence is a long run-on stuffing route names, rates, and return fields into one clause, making it harder to scan than necessary.

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?

There is no output schema, so the description must convey returns, which it does (quote, rate, WAN balance, solvency flag, approve/sell calls). Annotations cover the safety profile, and the skill pointer covers the follow-on execution path. Only the amount's expected format is left unaddressed for a comparison-oriented read 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?

One parameter ('amount') with 0% schema description coverage, so the schema carries no semantics. The description implies the amount is denominated in xWAN and references per-xWAN rates, adding units meaning, but gives no guidance on format, precision, or string-vs-number. Baseline 3 for a single lightly-documented parameter.

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+resource: it reads the WAN that an xWAN amount converts into across routes (xWAN Express, XFlows vesting tiers). The exact output contents (quote, rate, WAN balance, solvency, approve/sell calls) are named, so an agent knows what it gets. Somewhat jargon-dense, but the purpose is 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?

Implies usage through 'No route is recommended; the owner chooses' and by pointing to the wanchain-xwan-express skill 'covers selling,' which suggests this tool is for pre-sale option comparison rather than execution. It never explicitly states when to call this versus other tools, so usage is inferred rather than spelled out.

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