getTradeQuote

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

No annotations provided, so description carries full burden. It returns estimated receive amount, fees, gas cost, slippage. States agent must display quote to user. Warns not to call without valid token codes. Could mention idempotency or rate limits, but overall strong 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?

Well-structured with clear sections and bullet points, but slightly verbose. Front-loaded with purpose and returns. Could trim some redundancy in agent hints, but every sentence adds value.

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 5 parameters, 2 enums, no output schema, and complexity of two trade directions, the description is remarkably complete. It covers usage, prerequisites, token code sources, and agent responsibilities. No gaps for effective invocation.

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 0%, so description must compensate. It explains tradeType (1=purchase, 2=redeem) and token code orientation for each direction. Does not explain quoteMode or fromTokenAmount in detail, but provides enough context for typical usage. Adds significant value beyond schema.

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 it gets a price quote for purchase or redeem trades, specifies the two trade types with token code direction, and distinguishes from siblings like executePurchase, executeRedeem, and getBizTokenPriceList. The verb 'Get' and resource 'TradeQuote' are well-defined.

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?

Explicitly says to use before executing trades, lists alternatives (getBizTokenPriceList for prices only), and instructs to first call getPayTokenList/getBizTokenList to resolve token codes. Agent hints reinforce correct usage and warn against skipping this step.

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