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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safe-read profile is covered. The description adds useful context beyond that: it does not execute the intent, it is not a guaranteed quote, both chains must be supported EVM chains, and there is a $0.007 cost. That is meaningful behavioral disclosure, though nothing about rate limits or freshness of the analysis.

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?

Purpose is front-loaded in the first sentence, followed by placement guidance and caveats; the $0.007 cost is tucked in without disrupting flow. Three sentences, little waste, though the enumeration of dimensions is repeated between the first and second sentences.

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?

An output schema exists, so return-shape explanation is unnecessary, and annotations carry the safety profile. For a read-only analysis tool with 100% schema coverage, the description supplies enough scope, caveats, and cost context. It could say a bit more about what 'supported EVM chains' excludes, but overall it is complete.

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% and two params carry enums, so the schema fully documents fromChain, toChain, tokenIn, tokenOut, and amountUsd. The description adds no syntax or format detail beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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 domain (ERC-7683 cross-chain intent execution) and enumerates the outputs it produces — profitability analysis, gas costs, competition level, recommendations — so the agent knows exactly what it returns. The negative scope ('does not execute the intent') further bounds it. It does not explicitly name a sibling like util.intent_router, so sibling differentiation is implied rather than stated.

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 a clear placement in a workflow ('Use before evaluating an ERC-7683 cross-chain intent') and lists the comparison dimensions. It also warns against misinterpreting the output as a guaranteed quote. No alternative tool is named for when this isn't the right choice, so it stops short of full when/when-not guidance.

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