Get current rates

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is clear. The description adds that it returns current rates and supports filters, but doesn't disclose pagination behavior or rate limits. Given the annotation coverage, this is acceptable but not enriched.

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?

Two sentences that are front-loaded with the action and provide a usage example. No redundant or unnecessary 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?

The output schema exists so return values are covered. The description covers the primary purpose and filters. However, it does not mention the 'additionalProperties: true' in the input schema, which could lead to unexpected behavior if an agent passes extra fields. Otherwise, for a read-only list tool, the description is fairly complete.

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 100% with each parameter having a description. The description reinforces that filtering by symbol, category, or provider is possible, but does not add new meaning beyond what the schema provides. The 'limit' parameter is not mentioned in the description but is documented in the 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 the tool lists current rates across providers with optional filters, and provides an example query ('what is the best yield on BTC right now?'). This distinguishes it from sibling tools like get_rate_by_symbol or get_rate_history which are more specific.

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 says 'Use this to answer...' which gives a concrete use case. However, it does not mention when not to use this tool or suggest alternatives among the many sibling tools, missing some guidance for an AI agent.

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