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

Annotations already declare readOnlyHint=true, so the safe-read nature is covered. The description adds that the result is in USD and what it is used for, but does not disclose freshness, volatility, or why idempotentHint=false despite returning a price.

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 short sentences with the primary behavior front-loaded. The second sentence carries useful context about USD denomination and common uses, though it could be tightened.

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?

Adequate for a simple one-parameter getter with rich schema coverage and no output schema. However, it omits the key sibling distinction from get_oracle_prices and does not mention price freshness, which matters for a non-idempotent oracle lookup.

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 only parameter is fully documented in the schema, including examples (BTC, ETH, RUNE), so schema coverage is 100%. The description adds no syntax or format detail beyond restating that the symbol selects the asset.

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 and resource: returns the oracle price for a specific asset symbol. Clear on its own, but it does not distinguish itself from the sibling tool get_oracle_prices, so an agent must infer singular vs. plural behavior.

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?

Provides domain context (protocol calculations and limit order pricing) but gives no explicit when-to-use guidance, no prerequisites, and no comparison to the obvious alternative get_oracle_prices. The choice between this tool and its plural sibling is left to inference.

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