refresh_pairs_cache

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

Discloses that without arguments it re-acquires all pairs, and specifying a pair only highlights that pair's rate while still refreshing all. No annotations provided, so description carries full burden; it is transparent about the forced cache update.

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 concise sentences with front-loaded category. Every word adds value; no fluff.

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 no output schema and a single optional parameter, the description fully covers purpose, behavior, and parameter semantics. No gaps.

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% and description adds critical nuance: the 'pair' parameter only affects display, not which pairs are refreshed. This goes beyond the schema's description.

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?

Description clearly states it refreshes the TTL cache for fee rates, specifying the endpoint (/spot/pairs) and the domain (fees/maintenance). It distinguishes from sibling analysis tools by indicating it's a maintenance action.

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 states when to use (to immediately reflect latest fee rates at campaign boundaries) and describes default behavior (1h TTL). Does not mention when not to use or alternatives, but the context is clear.

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