Hedera: hederaTokensSwapQuote

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value by explaining 'crypto prices change every second', which justifies the idempotent but volatile nature. It does not contradict annotations; instead it complements them.

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 consists of two concise sentences. The first sentence states the core purpose, and the second provides urgency and mode options. Every sentence adds value with no wasted words.

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?

Given the tool's complexity (7 params, two modes), the description covers the essential aspects: purpose, freshness, and modes. It lacks details about the return format (no output schema), but for a swap quote tool, the response structure is somewhat standard. The description is adequate but not fully comprehensive.

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 provides descriptions for all 7 parameters (100% coverage), so the description does not need to add much. It mentions 'exact input' and 'exact output' modes, which relate to the amount, exactOutputAmount, and isExactOutput parameters, but the schema already explains these. Thus, baseline score of 3 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 clearly states it gets 'current USD price and swap quote' for Hedera tokens, using a specific verb and resource. It distinguishes from sibling tools like ethSwapQuote, bscSwapQuote, etc., which are for other chains, by specifying 'Hedera tokens'. It also mentions two modes (exact input/output), further clarifying its purpose.

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 advises to 'ALWAYS fetch fresh' due to rapidly changing prices, providing a clear usage guideline. It mentions the two modes (exact input/output) which guides when to use which. However, it does not explicitly state when not to use this tool or name alternatives, but the context of sibling tools implies chain-specific usage.

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