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

With no annotations provided, the description carries the burden and does substantial work: it explicitly discloses that the quote is not a live protocol quote but an honest gas-based estimate. This is exactly the kind of behavioral detail an agent needs to avoid misrepresenting the result. It does not disclose error cases or edge cases like unknown chains, but for a read-only estimate tool the core caveat is well covered.

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?

The description is compact and efficient: one sentence states the purpose and the necessary inputs. The critical caveat (honest gas-based estimate, not a live protocol quote) is front-loaded within the first clause. It loses one point because it lacks a tiny bit of structured guidance on parameter semantics, but overall it is appropriately sized and well organized.

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?

The description is adequate for a simple estimate tool but has clear gaps: it does not explain the meaning of the six schema fields, does not reconcile the described 'amount' parameter with the schema, and does not say what the output looks like. The massive sibling list and the presence of related crypto/fee tools make the lack of explicit differentiation slightly more costly. Still, the essential caveat and main inputs are present, so it is a minimum-viable definition.

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?

The schema has 100% coverage but the parameter descriptions are useless: every property is described with 'to process,' 'dest to process,' etc., which gives no semantic meaning. The tool description names fromChain and toChain and mentions optional amount, but the schema has no amount field at all and includes six fields (to, dest, from, source, toChain, fromChain) with no explanation of which are required or what values they accept. The description fails to compensate for the schema's uninformative parameter labels and even introduces a parameter (amount) that is absent from the schema.

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 clearly states the verb (estimate), resource (cross-chain bridge fee), and the unique differentiator (honest gas-based estimate, not a live protocol quote). It distinguishes itself from potentially similar crypto/fee tools by explicitly clarifying what it is not. However, it does not explicitly name a sibling alternative, so it stops short of a full 5.

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 says to provide fromChain, toChain, and optional amount, and frames the tool as an estimate for bridge fee from gas costs. It implicitly tells the agent this is the tool when an honest gas-based estimate is acceptable rather than a live quote, but it does not explicitly name an alternative tool or state when not to use it. It provides no explicit exclusion or alternative routing, so it is clear but not fully explicit.

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