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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the LI.FI API, which hints at an external dependency and potential network calls, but does not explicitly state whether the operation is read-only, what errors may occur, or any rate limits. This is a modest level of transparency but insufficient for a tool that could have side effects or fail due to external service issues.

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 a single, clear sentence with no fluff, front-loading the core purpose. It is appropriately concise, though it could be slightly more structured with separate sentences for scope and constraints, but it remains efficient and easy to parse.

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 tool has six required parameters, an external API dependency, and a schema with zero descriptions, the description is far too sparse. It does not explain parameter semantics, provide usage examples, or note any limitations. While an output schema exists, the absence of parameter guidance makes the tool difficult to invoke correctly. The description is not complete enough for an agent to use it reliably.

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 zero descriptions for its six parameters, so the description must compensate. However, it only vaguely suggests that parameters define a bridge request (from/to chain and token, amount, address) without explaining formats, enumerations, or unit expectations (e.g., wei vs. decimal). The description does not clarify how to specify chain names or token identifiers, leaving significant ambiguity for an agent.

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 states a specific verb ('Calculates'), a clear resource ('lowest-slippage bridge routes'), and a scope ('across EVM and Solana'), while also naming the underlying API (LI.FI). This clearly distinguishes it from sibling tools like contract_security_screener and dex_liquidity_router, which handle different functions.

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 implies the tool is for bridging across chains, but it does not explicitly state when to use this tool over alternatives like dex_liquidity_router for on-chain swaps. There is no guidance on prerequisites or when not to use it, leaving the agent to infer the usage context from the tool name and function.

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