blueDEX

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

With no annotations, the description carries the full burden, and it does a good job: it discloses that the transaction is unsigned, shows the verification block fields, and warns to verify before signing. It could go further by noting that it performs no on-chain mutation itself, but 'unsigned transaction' and the sign-only-if-allowlisted warning make the key behavior clear.

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 front-loaded: purpose, return format, verification block, and signing warning all appear in two sentences. Every sentence adds essential information and there is no filler.

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?

This is a security-sensitive, multi-chain tool with no output schema and no annotations, yet the description leaves out key context such as the prerequisite of calling get_swap_quote, the meaning of minBuyAmount and approvalTarget, and how to handle amount units. The verification warning is valuable, but overall the description is incomplete for correct usage.

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 only 33%, and the description does not compensate. It does not explain the units of 'amount', the meaning of 'slippageBps', or how the source, buy, and sell fields relate to the quote. The nested buy/sell objects and the native token convention are only covered inside the schema, not in the description.

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 identifies the verb 'Build' and the resource: 'an unsigned transaction for a quoted swap.' It also distinguishes itself from get_swap_quote by focusing on transaction construction, and from plan_route by returning EVM/Solana unsigned transaction data.

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 clearly states that the tool is for a quoted swap, so the agent knows it must be preceded by quote generation. It provides an explicit safety precondition: sign only if routerAllowlisted is true and addresses match get_meta's allowlist. It does not explicitly enumerate when not to use it relative to siblings, but the 'quoted swap' context is sufficient.

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

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

With no annotations, the description carries the disclosure burden and does it well: it returns a deposit address, funds are custodial only at the venue during the swap, and blueDEX never holds funds. It does not cover failure/expiry behavior or auth/rate limits, so it is strong but not exhaustive.

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?

Three sentences with no filler: purpose, operational flow/return value, and custody model are each addressed in sequence. The ID lookup hint is a useful, non-redundant addition.

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 definition covers the core return value and the full user flow, plus the custody nuance, and there is no output schema to contradict. It leaves refund/expiry behavior to the schema, but the absence of status/fee details is a minor gap rather than a blocking one.

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 coverage is 100%, so baseline is 3; the description adds meaning by explaining that `from` is sent to the returned deposit address and `to` settles to `settleAddress`. The instruction to use list_instant_assets for ids also clarifies parameter values beyond the schema examples.

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 opens with a specific verb ('Open') and resource ('INSTANT shift') and clearly scopes the tool to assets with no on-chain DEX route, listing Tron, BTC, and cross-chain. This distinguishes it from the swap/route siblings even without naming them.

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 states the selection condition: use this when there is no on-chain DEX route, for Tron/BTC/cross-chain assets. It also points to list_instant_assets for valid IDs. It does not explicitly name alternatives or when-not-to-use, but the context is clear enough for an agent to choose it.

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

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not mention whether the operation is read-only, any rate limits, data range limitations, or the structure of the returned candles (e.g., whether volume is included). The description is purely declarative and does not cover safety or side-effect implications. While the tool is likely safe, the absence of any such disclosure makes it hard for an agent to assess trust or handle unexpected responses.

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, straightforward sentence that front-loads the core purpose ('OHLCV candles') and immediately specifies the token selection rule. The timeframe list is appended efficiently without fluff. Every word earns its place; there is no redundancy or unnecessary detail. This is an exemplar of concise writing for a simple data-fetch 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?

For a tool with only 3 parameters and no output schema, the description covers the essential purpose and the main selection criterion. However, it omits a few pieces that would strengthen completeness: it does not explicitly state what the response contains (candles with OHLCV, timestamps, etc.), whether there are pagination limits, or how historical depth is determined. It also does not mention that the tool is read-only, which for a charting tool is a notable behavioral gap. Overall, it is adequate for a basic call but falls short of fully equipping an agent to handle edge cases or validate results.

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 coverage is low (33%), as only the timeframe parameter has a description in the schema. The tool description compensates partially: it explicitly lists the supported timeframes, which adds semantics beyond the enum, and it clarifies that the address refers to a token and that the pool is chosen by top liquidity. However, it does not explain the 'chain' parameter beyond the enum names, nor does it hint at the expected format for the address (e.g., checksummed contract address). The added value is present but not fully compensatory for the schema gaps.

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 identifies the tool's function: retrieving OHLCV candles for a given token on its top liquidity pool. It specifies the resource (token) and the selection scope (top pool by liquidity), and it also lists the available timeframes. This distinguishes it from the trading-focused sibling tools like build_swap_transaction and get_swap_quote, which serve different purposes. The verb 'get' and the explicit 'OHLCV candles' convey the exact action.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites (e.g., token address format), or scenarios where one might prefer another tool. The only useful context is the implied 'if you need chart data, use this,' but there is no explicit comparison or exclusion. For a tool that likely sits alongside many trading operations, this omission leaves an agent to infer selection criteria from the purpose alone.

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

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

No annotations are provided, so the description carries the full burden. It discloses the possible statuses and the presence of tx hashes, but omits error handling, rate limits, or what happens for invalid ids. It's a read-only operation by nature, but that's not explicitly stated.

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?

A single sentence that front-loads the purpose and lists statuses compactly. It's efficient, though the status list adds length; still, every part contributes to understanding.

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?

For a simple status tool with no output schema, the description covers the main data (statuses and hashes) but lacks details on response structure, error cases, and polling behavior. It's adequate but not exhaustive.

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?

With 0% schema coverage, the description must explain the 'id' parameter. It does so by linking it to create_instant_shift, indicating it's the shift identifier. This adds meaning beyond the bare schema, though format/constraints are not detailed.

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 ('get') and resource ('instant shift') with the source of the id. Clearly distinguishes from siblings like create_instant_shift by referencing it as the origin of the id, making the tool's role unambiguous.

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?

Implies usage after creating an instant shift via create_instant_shift, which is clear from the description. However, it doesn't explicitly state when not to use it or mention alternatives, though siblings like build_swap_transaction are obviously different.

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

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

With no annotations, the description carries the full burden. It conveys that this is a read-only, public data retrieval ('published transparency data') and spells out exactly which transparency categories are included. It does not discuss caveats like staleness or auth, but for a zero-parameter read endpoint this is a clear behavioral disclosure.

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 concise sentences with no filler; the data categories are listed compactly and the use case is front-loaded. Every sentence earns its place.

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?

For a zero-parameter tool with no output schema, the description fully compensates by naming the data contents and the intended audit use case. An agent can decide whether to call it and what to expect without needing more detail.

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?

There are zero parameters and the input schema has 100% coverage, so the baseline is 4. The description has no parameter-specific details to add, and none are needed.

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?

Description clearly identifies the tool as returning blueDEX's published transparency data and enumerates the specific contents: treasury addresses, router allowlist, fee schedule, and paused venues. It also gives an explicit purpose (auditing quotes/transactions), which distinguishes it from the operational swap/quote/route siblings.

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 explicitly states the intended use case: 'Use this to audit quotes and transactions.' It does not enumerate when-not-to-use or name a specific alternative, so it falls just short of a 5, but the context signals show no overlapping read-verification sibling.

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

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

With no annotations provided, the description carries the full behavioral burden. It discloses return contents (winning quote, all venue quotes, fee recipient) and cross-chain support, which is useful. However, it doesn't explicitly state that this is a read-only operation (no swap execution) or mention any side effects, rate limits, or auth requirements. The lack of a clear 'does not execute' statement leaves room for misinterpretation.

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 sentences with no fluff. The purpose is front-loaded, and the additional details (transparency of venue quotes, fee recipient auditability, cross-chain support) are concise and relevant. Every sentence earns its place.

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?

For a tool with nested objects, 4 parameters, and no output schema, the description is reasonably complete on return behavior but lacks parameter guidance and limitations. It mentions cross-chain on EVM but doesn't clarify single-chain usage or how to specify chains/addresses. It also doesn't mention potential errors or constraints. There are gaps that an agent would need to infer or probe.

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 only 50%, so the description should compensate for undocumented parameters. It does not mention any parameters at all – sell, buy, amount, or slippageBps. The schema provides some description for amount and slippageBps, but the nested sell/buy objects lack top-level descriptions. The description adds zero value on how to structure inputs, leaving the agent to rely on the schema alone.

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 clear verb ('Get') and resource ('best swap route across DEX aggregator venues') and adds specific return details (winning venue quote, all quotes, fee recipient). It doesn't explicitly name sibling alternatives, but the scope is distinct enough to separate it from build_swap_transaction or plan_route.

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 use for obtaining quotes before building a transaction, and mentions cross-chain support as a capability, but it never states when to choose this over siblings or any exclusions. There's no explicit when-not guidance, so the agent must infer usage from the tool name and context.

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

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

No annotations are provided, so the description carries the full burden. It states that the tool returns ids, which implies a read-only retrieval, but it does not explicitly disclose the absence of side effects, permissions, or rate limits. It adds useful context about asset types but lacks an explicit statement of behavior beyond the listing operation.

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 two sentences, front-loaded with the core purpose and immediately followed by a practical example. No superfluous words or redundancy. Every sentence earns its place, making it highly efficient for an agent 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?

For a simple, parameterless list tool, the description provides sufficient context: what assets are listed, what the output looks like (ids), and how the output is used. While it does not specify the exact response structure (e.g., array of objects), the given example and purpose are enough for an agent to call it correctly. Given the low complexity, this is adequately 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?

The input schema has zero parameters, so the baseline is 4. The description correctly does not attempt to explain parameters that don't exist. It adds value by mentioning the example id and its purpose, but since there are no parameters, there is nothing further to clarify.

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 tool lists assets reachable via the INSTANT lane, specifies the corridors (Tron/USDT-TRC20, BTC, stablecoin), and gives an example id. It explicitly mentions the intended consumer (create_instant_shift), which distinguishes it from sibling tools like list_onramps. The verb 'list' and resource 'instant assets' are specific and unambiguous.

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 when to use the tool: to obtain asset ids for create_instant_shift. It also distinguishes from the on-chain DEX route, suggesting a clear context. However, it does not explicitly name alternatives or state when not to use it, but the provided purpose is sufficiently clear for an agent to infer the appropriate scenario.

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

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

With no annotations, the description carries the full burden. It discloses that blueDEX operates none of these ramps and takes no custody, and it explains the nature of the results (human-mediated vs agent-callable, BTC-only vs multi-asset). It does not explicitly state that the tool is read-only, but the list-like behavior is strongly implied and the domain context adds genuine value.

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 dense 100-word paragraph. Every sentence adds a distinct fact, but the syntax is clunky (e.g., 'Reputable INDEPENDENT fiat->crypto on-ramps blueDEX signposts') and the information could be more scannable as bullets. It is front-loaded with purpose, but the verbosity hurts clarity.

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?

For a zero-parameter, no-output-schema list tool, the description is largely sufficient. It explains what the list contains, the distinguishing constraints, and even gives an agent a direct instruction on when to present it. The only gap is a missing explicit output format, but for a signposting tool this is minor.

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 tool has zero parameters, so the schema already covers everything. The description goes beyond the schema by explaining the selection criteria and content of the list, which is useful for an agent deciding when to use the tool. The baseline of 4 for zero-parameter tools is appropriate.

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 conveys that the tool surfaces reputable independent fiat-to-crypto on-ramps, which is distinct from swap/bridge siblings. However, the opening sentence is grammatically convoluted ('blueDEX signposts so a human principal...'), making the core action less direct than it could be.

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 explicitly states when to surface this tool ('when a human asks how to get their first crypto') and hints at alternatives by pointing to 'the instant lane or a quote' for onward bridging. It also distinguishes agent-callable ramps (Transak, MoonPay) from human-mediated ones, giving practical selection guidance, though it does not directly contrast with sibling tools.

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

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

No annotations are provided, so the description carries the full burden. It discloses that the tool composes non-custodial DEX swaps and custodial-at-venue bridges, returns ordered legs with custody and fees, and describes the output structure. It does not explicitly state read-only behavior, but as a planning tool, this is implied. It adds context about fee disclosure and custody per leg, which is valuable.

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 succinct, front-loaded with the primary purpose, and includes a concrete example. Every sentence serves a purpose: defining the tool, illustrating the output, and guiding execution. There is no fluff.

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?

For a complex planning tool with no output schema, the description is thorough: it defines inputs, explains the composition of legs, describes the return (ordered legs, total output), and provides execution instructions. An agent can correctly call this tool and understand how to use the results without additional documentation.

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%, so parameters are already documented. The description adds value beyond the schema by explaining the dual nature of `from`/`to` (instant id or DEX token) and providing an example of how to express a route. It also clarifies that `amount` is integer base units of `from`, which is already in schema but reinforced with the example. The description enriches the semantic understanding.

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 tool's purpose: planning the cheapest multi-hop route between any two assets, composing DEX swaps and instant-lane bridges. It includes an example that illustrates the concept and differentiates it from sibling tools like build_swap_transaction and create_instant_shift by emphasizing that this is a planning tool, not an execution 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?

The description explicitly instructs the agent on how to use the results: 'Execute legs in order: DEX legs via build_swap_transaction, bridge legs via create_instant_shift.' This tells the agent exactly when to use this tool (planning) and when to use alternatives (execution), providing clear routing guidance.

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

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

With no annotations, the description carries the full burden of behavioral transparency. It discloses that the tool is non-custodial, returns a plan of unsigned swaps, includes only gas-positive legs, rides the sweep fee on one leg, and requires the user to approve each leg's approvalTarget and sign. This goes well beyond the schema and gives the agent an accurate model of what happens before, during, and after the call.

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 four compact sentences with no filler. The first sentence front-loads the core purpose, followed by input handling, output plan characteristics, and supported chains. Every sentence contributes essential information without redundancy.

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?

This tool has no output schema and no annotations, so the description must provide sufficient context for correct invocation. It explains the plan output, the signing/approval flow, and supported chains. It does not detail the exact structure of the returned plan or edge cases (e.g., what happens when no gas-positive legs exist), but the description gives the agent enough to call the tool and understand the result at a high level. Minor gaps prevent a 5.

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%, so the baseline is 3. The description adds minimal semantic value: it reiterates the default USDC, the dust list shape, and that the caller knows their own balances. These points are already present in the schema, so the description does not meaningfully enhance parameter understanding beyond what structured data provides.

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 action—'Consolidate many small leftover token balances (dust) into one token (default USDC) on an EVM chain'—with a clear verb and resource. It is distinct from sibling tools like get_swap_quote or build_swap_transaction, which handle general swaps, while this tool is specifically for sweeping dust balances.

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 clearly implies when to use this tool: when you have multiple small leftover token balances to consolidate into one token. It does not explicitly exclude use cases or reference alternatives, but it provides enough context (e.g., 'you know your own balances', supported chains) for an agent to recognize the intended scenario. There are no explicit exclusions, but the usage context is clear.

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