Binance Smart Chain: bscSwapQuote

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's main burden is adding context beyond that. The description mentions using 'Uniswap X or 0x' as routing protocols, which is useful behavioral context. It also provides the native BNB address, aiding correct invocation. No contradictions with annotations.

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 succinct sentences. The first states the core purpose and the second provides a critical usage hint. No redundant information. Front-loaded with the action and resource.

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 tool lacks an output schema, so the description should explain what the quote contains (e.g., price, slippage, expiry). It does not mention the return value format or any additional behaviors like rate limits or availability. Given the complexity of a swap quote, this is a significant gap.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds value by specifying the Ethereum address for native BNB (0xEeeee...), which is not in the schema. This clarifies the fromTokenAddress parameter for a common use case, raising the score above baseline.

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: 'Get swap quote for BSC tokens.' It specifies the blockchain (BSC) and the function (swap quote), distinguishing it from other swap quote tools for different networks like ethSwapQuote or polygonSwapQuote. The verb 'Get' and resource 'swap quote' are specific.

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 implicitly indicates usage for BSC tokens and provides a key hint for using native BNB via a special address. However, it does not explicitly state when to use this tool versus similar swap quote tools or when not to use it. The context is clear enough for agents familiar with the domain.

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