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

Annotations already declare readOnlyHint and idempotentHint, but the description adds valuable behavioral context: prices change every second and fresh data must always be fetched. This goes beyond the structured annotations by addressing freshness/liveness, though it doesn't detail response format or edge cases.

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 concise sentences, front-loaded with the tool's core purpose. Every word adds value, and the freshness warning is both necessary and memorable.

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 7 parameters and no output schema, the description covers the essential purpose, mode distinction, and freshness requirement. It doesn't detail the quote response structure, but the name and summary are sufficient for a simple read-only quote tool. Slightly more detail about output could push it higher.

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 the baseline is 3. The description adds a high-level explanation of exact input versus exact output modes, but the schema already explains the 'amount' and 'exactOutputAmount' parameters clearly. No additional parameter-specific meaning is provided.

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 gets a current USD price and swap quote for Hedera tokens, using a specific verb ('Get') and resource ('Hedera tokens'). It also distinguishes this from siblings by naming the Hedera context and the two quote modes.

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 clearly implies when to use the tool: for Hedera token swap quotes, and emphasizes 'ALWAYS fetch fresh' to reinforce real-time usage. However, it does not explicitly mention alternatives or exclusions, such as using chain-specific swap quote tools like baseSwapQuote for other chains.

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