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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, but the description adds substantial context beyond them: the x402/Base payment model, the prepaid x-credit-token header for unlimited calls, one free call per day, and no API key requirement. It also explicitly states nothing is reserved or paid and enumerates the returned fields, which is exactly the extra behavioral disclosure a quote tool needs.

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-loads the purpose as a question and then packs a lot of relevant detail (asset formats, outputs, payment terms, free tier) without filler. It is longer than most definitions and the opening rhetorical question is a slightly indirect way to lead, but no sentence is wasted.

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 a 3-required-param, quote-only tool with full schema coverage and an output schema, the description covers everything an agent needs: identifier formats, what is returned, that it is non-binding, and the pricing/auth model. Even the return-value list is redundant with the output schema but harmless.

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, but the description adds real meaning by explaining how asset identifiers may be written (symbol like USDC for on-NEAR, USDC@base for another chain, a NEAR token account, or a 1Click asset id). That naming convention is not recoverable from the bare schema strings 'Asset you pay with' and 'Asset you want'.

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 (indicative swap quote through NEAR Intents) and clearly distinguishes itself from the sibling near_swap by emphasizing it is a quote, not an execution. It also scopes the asset universe (NEAR, USDC, USDT, BTC, SOL, cross-chain), so an agent can distinguish it from near_swap_status or base_swap without opening a 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 clear context for when this applies — an indicative price check where 'nothing is reserved or paid' — and notes the cost model (paid per call, free daily call), which shapes when an agent should invoke it. It stops short of naming the sibling to use for the actual swap (near_swap), so there is no explicit alternative routing.

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