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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds valuable context beyond annotations: data provenance (CoinGecko markets + DeFiLlama DEX volume), keyless access, and the $0.03 USDC cost. This gives an agent accurate expectations about external dependencies and cost.

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?

A dense, front-loaded single sentence provides the signal definition, z-score formula, data sources, keyless access, and pricing. There is no filler; every clause contributes information needed to decide whether and how to call the tool.

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 simple one-parameter optional-input tool with an output schema and strong annotations, the description is largely complete: it defines the signal, explains the calculation basis, and notes cost/auth. It could include a concrete input example, but that gap is minor given the parameter is optional and free-form.

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 input parameter has 100% schema coverage, so the baseline is 3. The description does not elaborate on how to format or what specific product parameters are accepted, but the parameter is optional and the schema already describes it as JSON or text.

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 description clearly identifies the resource ('crypto volume-anomaly alerts') and gives a precise, measurable definition: assets whose 24h turnover (volume/mcap) is anomalously high versus their cohort by z-score. This is specific enough to distinguish it from sibling market and risk tools.

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 explicitly frames when it is useful: for arbitrage bots seeking early pump/unusual-activity signals. It does not name alternative tools or list exclusions, but it provides clear contextual triggers for selecting this tool.

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