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

Annotations already declare readOnlyHint=true and openWorldHint=true, lowering the burden. The description adds meaningful behavior beyond those annotations: the operation is free with no API key required, the return contract is a quoteToken, and the follow-up execution step is named. This partially compensates for the absent output schema. Not a 5 because it omits quote validity window and rate-limit/failure behavior.

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?

Three sentences, each earning its place: core function plus scope, cost/auth requirement, and return contract plus workflow handoff. The primary purpose is front-loaded and there is no filler or repetition of schema content.

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 read-only 11-parameter, cross-chain tool with no output schema, the description covers the key decision points: what it returns (quoteToken), what to do next (ravn_execute), cost, and chain scope. It leaves gaps around quote expiry, rankingMode semantics, and failure handling, but the schema and annotations cover much of the remainder, so this is solid rather than exceptional for the complexity level.

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 73%, so the schema carries most parameter meaning. The description enriches several parameters — chain scope and native-token handling support inputChainId/outputChainId and the 0xEeee... sentinel, and 'no API key required' contextualizes apiKey — but it does nothing for the undocumented parameters (rankingMode, slippageBps, refundAddress) beyond what their enum and min/max constraints imply. Baseline 3 is appropriate given the high schema coverage.

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 opens with a specific verb and resource: 'Get a swap quote from RAVN', then narrows scope with 'same-chain or cross-chain, across 16 chains including native (non-wrapped) Bitcoin and Solana'. It clearly differentiates itself from the execution sibling by stating the quoteToken is passed to ravn_execute, and from ravn_health (venue discovery), ravn_status, and ravn_btc_prepare_send. No tautlogy; the resource and behavior are unmistakable.

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?

The description encodes an explicit workflow: call this tool to obtain a quote, then 'pass it to rav_execute to get a signable/broadcastable execution payload'. It also declares 'Free, no API key or payment required', so the agent knows no credential setup is needed. It stops short of a full 5 because it doesn't explicitly state when to prefer ravn_quote over ravn_btc_prepare_send or give a when-not-to-use condition.

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