bitflow_swap

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

With no annotations, the description carries the burden well: it discloses the public-endpoint rate limit (500 req/min), no-API-key access, wallet unlock requirement, mainnet-only restriction, and (via the schema's confirmHighImpact param) that >5% price impact needs opt-in. It does not state that this is an on-chain state-changing transaction with fees or what happens if slippage is exceeded, which keeps it out of the top score.

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?

Front-loaded with the action, then mechanism, then constraints — each line carries distinct information. The closing 'Tip' is marginally promotional but still routes the agent to a useful next call, so it 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 mutation tool with no annotations and no output schema, the description covers prerequisites, network availability, rate limits, and route behavior. The gap is the return value — it never says whether the call returns a tx ID, quote, or receipt, which matters when no output schema exists.

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 baseline 3 applies. The description only restates the tokenX/tokenY roles in prose and adds no meaning about amountUnit, fee presets, or slippage semantics beyond what the schema already documents.

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 and resource ('Execute a token swap on Bitflow DEX') and then narrows the mechanism ('aggregated liquidity', 'best route across all Bitflow pools'). An agent can separate this from sibling quote/discovery tools like bitflow_get_quote or bitflow_get_routes and from alex_swap by the named DEX.

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?

Prerequisites are stated explicitly: unlocked wallet, sufficient token balance, mainnet only, and a pointer to earning_opportunities. However, it never says when to prefer this over alex_swap or when to run bitflow_get_quote first, so the alternative-routing guidance stops short of the top band.

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