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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the bar is lower. The description adds real value beyond them: it clarifies the tool only produces unsigned material, that the wallet signs externally, and that nothing is submitted — a workflow-critical distinction.

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 tight sentences, front-loaded with purpose, then workflow, then the negative constraint. No filler, though the endpoint notation is slightly redundant ornamentation.

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 9-parameter tool with no output schema and near-zero schema description coverage, the description leaves the caller without enough to construct a valid request (which chain/token identifiers, amount units, slippage semantics) or to understand the shape of the returned unsigned material.

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 only 11% across 9 parameters, and the description explains none of them — fromChain/toChain/from/to/token/order/slippage semantics, address format, or whether amount is in source or target units are all unstated. With low coverage the description is supposed to compensate, and it does not.

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 (quote) plus the distinguishing scope (cross-chain, buy a meme) and the artifact returned (unsigned material + endpoint GET /api/xquote). It implicitly separates itself from the single-chain memeswap_quote, though it never names the sibling, so differentiation is left to inference.

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?

"when the user wants to buy a meme across chains" gives a usable trigger condition, but there is no when-not guidance and no explicit routing to memeswap_quote or memeswap_build as alternatives. Adequate but with a clear gap.

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