Get rates

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data behavior are covered. The description adds that rates are 'current' and limited to USDT/TRX, but it does not disclose freshness, caching, or failure behavior for live rate retrieval.

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?

A single compact sentence that front-loads the resource and scope. Every phrase adds information about the returned values and their invoice context.

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 zero-parameter read-only tool with no output schema, the description is nearly complete: it states the asset coverage and pricing basis. It could mention return format or freshness, but those are minor gaps given the tool's simplicity and existing annotations.

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 tool has zero parameters, so the baseline is 4. The description correctly avoids implying any inputs and reinforces which assets are covered, which is useful but not strictly necessary for invocation.

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?

States a specific verb/resource ('current USD prices of the supported coins') and names the exact coins covered (USDT and TRX). It also distinguishes itself from the invoice-oriented siblings by clarifying the pricing context used for USD-priced invoices.

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 implies usage for USD pricing and invoice contexts, but it does not explicitly say when to call this versus the invoice-focused sibling tools or whether it should be used before creating/reading invoices. The context is helpful but leaves selection guidance mostly inferred.

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