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

Annotations already declare readOnlyHint=true and destructiveHint=false, making the read-only nature clear. The description adds useful context about sellAmount flexibility ('$5', 'max') and the normalized return format ('conditionalOrderHandoff'), which goes beyond the schema. No contradictions found.

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 primary action and immediately useful details about parameter formats and return type. No filler or 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?

The description covers the purpose, key parameter flexibility, and return type, but leaves gaps: buyTokenAddress and sellTokenAddress are optional in the schema yet logically needed for a swap, and the meaning of 'conditionalOrderHandoff' is undefined (no output schema). For a moderate-complexity tool, more prerequisite or return context would help.

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%, and the schema already details sellAmount's formats and units. The description restates the sellAmount flexibility but adds no new parameter-level information beyond what's in the schema. It does clarify exact-input semantics, which is consistent with the schema's 'spend' interpretation.

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 verb and resource: 'Quote an exact-input BSC swap.' It distinguishes from sibling chain-specific quote tools (e.g., ethSwapQuote, polygonSwapQuote) by naming BSC and specifying exact-input, and it adds precision by mentioning the return type.

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 clear context: it's for BSC swaps with exact input amounts, and it notes the output is for 'explicit entry or exit orders.' However, it does not explicitly contrast with alternatives like exact-output quotes or other chains, relying on the title/name for differentiation.

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