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

Annotations already cover read-only, open-world, non-idempotent, non-destructive semantics, so the bar is lower. The description adds genuinely non-schema information: per-call pricing, the x402/USDC-on-Base payment requirement, and that failed calls are not charged — real operational context an agent must account for.

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 sentences, zero filler: the contents come first, then cost/payment/failure policy. Every clause carries information an agent needs before invoking or budgeting the call.

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 multi-source composite tool with no output schema, the description enumerates what comes back and nails the billing model. It doesn't say how the data is structured (separate sections vs merged) or whether unavailable feeds null out or error, which would matter for a bundle like this.

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 100% and the single parameter is already documented with an example (BTC). The description only reinforces 'one coin', adding no ticker formatting, casing, or exchange-scope detail beyond the schema. Baseline 3 is appropriate.

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 concrete verb-and-resource framing ('Everything for one coin in one call') and enumerates the exact data bundled: price, funding/OI, order book, liquidations, whale orders, news. This makes it clearly distinguishable from the single-purpose siblings like prices, orderbook, liquidations, and news.

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 'one coin in one call' framing implicitly tells the agent to use this instead of fanning out across the individual sibling tools. It also gives a decisive usage condition via cost (USD 0.005) and payment rails, but gives no explicit when-not-to-use or pointer to the cheaper/free siblings like prices_free or sentiment_free.

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