Rates and sources

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

No annotations are provided, so the description carries the full disclosure burden. It implies a static reference read but never states that it is read-only, whether it is cached or live, whether auth is required, or how frequently the 'default rates' change — all of which matter for a pricing-adjacent lookup.

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 fragment that front-loads the payload contents with zero filler. It is efficient, though as a bare noun phrase it lacks a framing clause that would make the intent immediately actionable.

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?

With no annotations and no output schema, the description is the only source of information, and it never defines what a 'platform' is, what 'options' contains, or the shape of the returned records. It covers the broad content categories, which is the minimum viable level, but leaves the agent guessing about the return format.

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 takes zero parameters and the schema is an empty object, so there is no parameter semantics to document. The baseline of 4 applies; the description cannot add parameter meaning that does not exist.

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 names the resource and its payload (default rates, options, official source pages) but supplies no verb, so it reads as a data dump rather than an action an agent can request. It also does nothing to distinguish itself from siblings like fee, payout, and price_for_target, which plausibly cover overlapping rate/price territory.

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?

There is no statement of when to call this versus fee, price_for_target, or compare, and no prerequisites or context are given. The agent must guess from the name alone whether this is a reference lookup or a computation.

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