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

Goes well beyond the readOnly/idempotent annotations: discloses dynamic x402 pricing with a $0.01–$0.30 USDC range and where the exact live quote appears, both auth paths (X-API-Key / Bearer, or settle x402 after HTTP 402), and a latency/token cost hint ('prefer small limit (3–5)'). It also documents alternate response encodings (Accept header, ?format=compact, ?fields=, ?simple=true), which no annotation conveys.

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?

Purpose and output fields are correctly front-loaded, but the paragraph is overstuffed with semicolon-chained clauses and repeats the x402 dynamic-pricing statement almost verbatim twice. The signup URL and REST encoding notes are useful, yet the duplication costs space that could have gone to distinguishing sibling tools.

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 12-parameter, no-output-schema tool, the description closes the important gaps: it enumerates the returned fields, explains the kind modes and the recommended hunt recipe, and covers auth, pricing, and compaction. An agent can invoke it correctly and interpret the response without opening further docs.

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 already 100%, so the baseline is 3; the description earns extra by explaining what compact actually abbreviates ('keeps v5m/v1h/vu/mom') and by showing a validated parameter constellation for hunt mode (kind, window, sort_by, min_tvl, limit, full). It still leaves honor_sort, page_size, and filter_by entirely to the schema, so it is not a complete semantic layer.

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 ('rank pools by fee/TVL, fees, volume, APR, or TVL') plus the output contract (verdict SAFE/CAUTION/AVOID, risk_score, momentum_score, fee_velocity, bin_step_risk_tier, volume buckets, flags, citations). This is far more specific than the bare title 'Meteora DLMM pool brief' and separates it from the generic solana_dex_brief sibling.

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?

Gives an explicit when-to-use rule ('kind=hunt_pools for mid-risk hunt (SAFE+CAUTION; AVOID only with real volume_5m)') and an explicit when-NOT ('do NOT use top_pools_safe as hunt universe'), plus a concrete recommended call shape. However, the routing guidance is all at the parameter-mode level; no sibling tool is named as an alternative or exclusion, so an agent still has to infer when to pick meteora_pool_detail or solana_dex_brief instead.

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