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

Annotations already declare readOnly, idempotent, and open-world, but the description adds genuinely new behavior: a $0.001 USDC x402 charge per call, no API key or account needed, and a 402 response with payment requirements when unpaid. That is exactly the pre-call context an agent needs; only return shape and any rate limits are left unstated.

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?

The purpose is correctly front-loaded, but roughly half the text is a promotional block pointing at unrelated demo endpoints (including an NVDA Form 4 sample, which has nothing to do with crypto prices). Useful payment info is diluted by marketing copy.

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 paid, no-output-schema tool backing a 'does it meet the condition' check, the description never indicates what comes back — a boolean, the price, both? Given there is no output schema, that return-shape gap is the agent's remaining blind spot, though payment and auth behavior are well covered.

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 description coverage is 100%, and the schema itself documents the CoinGecko id format, the USD threshold examples, and the 'provide above, below, or move_pct_24h' exclusivity rule. The description only restates those concepts at a high level, adding no syntax or edge-case detail beyond the schema, so baseline 3 applies.

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 first sentence gives a specific verb and resource ('Check a CoinGecko asset price') plus the evaluated conditions ('USD threshold or 24-hour move condition'), so the operation is unambiguous. It does not explicitly contrast itself with the closely-named sibling watch_crypto_price, leaving the one-shot vs. persistent-watch distinction to inference from the tool names.

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?

Usage context is implied rather than stated: the payment terms and the free sample/watch endpoints signal this is a paid one-shot check with free alternatives. However, it never tells the agent when to pick this over watch_crypto_price (persistent monitoring) or check_now, which is the sibling decision that actually matters.

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