getReferencePrice

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

No annotations exist, so description fully owns transparency. It discloses return fields (buy/sell prices, timestamp, quota) and crucially states that prices are for reference only—managing expectations about data quality.

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?

Extremely concise with clear structure: one-line summary, bullet returns, important warning, use cases. Every sentence adds value, no redundancy.

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 simple query tool with 2 parameters and no output schema, the description covers return structure, caveat, and use cases. Minor omission: no mention of authentication or rate limits, but these are common and likely handled globally.

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 0%, so description must compensate. It implies symbol is the trading pair and paymentMethod filters by payment method, but does not enumerate valid values or formats for paymentMethod. Adequate but not detailed.

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 states 'Query the reference exchange rate for a specified trading pair' which is a specific verb+resource+scope. It clearly distinguishes from quote-related siblings by noting that actual trading prices come from the quote endpoint.

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?

Explicit use cases are provided: display approximate rates, compare prices, calculate estimated amounts before requesting a quote. The important note clarifies when not to use (for actual trading).

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