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 economic behavior (per-call price of $0.007) and the classification output shape, which is genuinely useful, but says nothing about permissions, rate limits, latency, or whether unlisted coins error or fall back to a default.

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 dense sentences plus a query-param hint, no filler, and the classification vocabulary is front-loaded. Leading with the price rather than the purpose is a minor structural oddity but still earns its place as decision-relevant information.

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-optional-parameter read tool with no output schema, the description covers purpose, return categories, and confidence, which is nearly everything needed. The remaining gap is the incomplete coin list, which undercuts the otherwise complete picture.

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%, so the baseline is 3, but the description actively narrows the parameter by listing only 'BTC, ETH, SOL, AVAX' while the enum accepts six values including LINK and XRP. That omission misleads an agent about which symbols are valid, so it scores below the do-no-harm baseline.

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 ('Market regime detection') plus the exact output vocabulary (TRENDING, RANGING, CRISIS, RECOVERY) and a confidence score, so an agent knows precisely what it gets back. It adds a scope cue ('single coin') that partly distinguishes it from regime_confluence, but never names siblings explicitly.

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 is only implied: 'for a single coin' suggests this is the per-asset entry point among the regime_* family, but there is no explicit when-to-use / when-not-to-use statement or named alternative. An agent must infer that regime_confluence or regime_transition covers other cases.

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