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

The description goes far beyond annotations: it states the tool is non-custodial, that Crank never signs or broadcasts the EVM leg, that funds are never held in flight, that the result is an unsigned evm_transaction to be broadcast by the user, and that idempotency_key replays the original order. This gives an agent an unusually clear behavioral model.

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 dense but well organized, front-loaded with purpose and process. It includes some repeat emphasis (never signs, never broadcasts, never holds funds in flight), but each sentence contributes actionable information and the length is reasonable for a complex bridge tool.

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?

Given the output schema exists, the description covers the most important operational facts: source chains, return shape, signing requirement, post-bridge workflow, fees, paper trading, and idempotency. It could still explain a few non-obvious params like pay_in_crank and caller_id, but an agent would be well equipped to call this tool correctly.

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 0%, so the description carries the burden. It meaningfully explains amount units, dst_token semantics, wallet_address, evm_sender, src_chain supported values, and idempotency_key. Some parameters like caller_id, pay_in_crank, and payment_header remain unexplained, which keeps this from being a 5.

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 a specific action — funding a Solana wallet from a major EVM chain — and explains it does this by building an unsigned EVM bridge order. It names the resource types involved (dst_token, wallet_address, evm_sender) and differentiates itself from nearby sibling concepts like bridge_out or jupiter_swap.

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?

It gives clear context for when to use the tool: cross-chain funding from supported EVM chains into Solana, then pairing with jupiter_swap or strategies once funds arrive. It lacks an explicit when-not-to-use statement or named alternatives such as bridge_out, but the workflow guidance is strong enough to route a caller.

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