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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description usefully adds that transaction material is 'unsigned' and only returned 'where available' (i.e., partial results possible) and that nothing is submitted — real context beyond the annotations, though no auth or rate-limit detail.

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?

Two short sentences, front-loaded with the core purpose and ending on the key boundary ('Does not submit'). Nothing wasted, though it is arguably too terse given the tool's complexity.

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, yet the description only gestures at the return ('unsigned transaction material where available') without covering the quote fields an agent would act on, and nine inputs remain largely undocumented. Adequate as a minimum, but thin for a 9-param cross-chain quote 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?

Nine parameters with only 11% schema description coverage, and the description adds no parameter meaning at all — no explanation of fromChain/toChain vs fromToken/toToken, slippage units, or the order/slippage semantics. The description fails to compensate for the coverage gap.

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 ('cross-chain route quote') and its output ('unsigned transaction material'), which cleanly separates it from the same-chain memeswap_quote sibling. The endpoint path (GET /api/xquote) confirms the operation. It stops short of explicitly naming the alternative tool.

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?

'Does not submit' implies this is a read/quote step that must be followed by a submission tool, but no sibling is named and no when-not-to-use condition is given. Usage is only implied, leaving the agent to infer that memeswap_build or a submit step comes next.

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