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

With no annotations, the description carries the full burden. It does disclose two useful behavioral traits — data provenance ('live market data, with source attribution') and the cost model ('$0.004/call via x402') — but says nothing about freshness/latency, caching, rate limits, or whether payment is required per call versus via a token.

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 tight sentences; the core capability is front-loaded and the pricing/provenance note is compact and earns its place for a paid x402 endpoint.

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 one-parameter read tool with no output schema and no annotations, the description covers the essential call context and hints at the return ('source attribution'), though it does not state the response shape (scalar vs. JSON with source fields) an agent should expect before paying.

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 single parameter has 100% schema description coverage including default (BTC) and examples, so the schema does the heavy lifting. The description only reinforces 'one token symbol', adding no syntax, casing, or format detail beyond 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?

States a specific verb+resource: the current USD price of a single token symbol sourced from live market data, plus source attribution. It is clear what the tool returns, but it does not differentiate from siblings like token_metrics or trading_signals, which an agent could plausibly confuse with a price lookup.

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 gives no explicit when-to-use guidance and never names an alternative among the many market-data siblings (token_metrics, trading_signals, bazaar_price_stats, us_equity_snapshot). Usage is only loosely implied by 'Current USD price for one token symbol'.

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