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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered; the description adds real value on top by explaining the score's anchor (50 = the study base rate), the coverage.note caveat about coins/timeframes the study misses, and 'read-only, no key, not financial advice'. It does not discuss latency, rate limits, or failure modes.

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 scale are front-loaded, and nearly every clause carries information (scale, patterns, input modes, caveats). It is dense and runs several ideas together with em-dashes, which slightly hurts scanability, but there is little padding.

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?

With no output schema, 7 optional parameters, and no required fields, the description does a good job of describing what comes back (score, patterns tagged by measured success rate, drawing points, coverage note). The only thin spot is that the precise return shape of drawing points and coverage is left implicit, but it is adequate for calling the tool correctly.

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 baseline is 3, but the description adds meaning the schema lacks: candles may be an array OR CSV text of 60-5000 rows, chain is only needed when the address is ambiguous, symbol maps to Binance USDT pairs, and shared tickers are never conflated. This genuinely reduces ambiguity about how to supply inputs.

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+resource (score a chart) and pins down the scale (1 = very bearish, 100 = very bullish) plus the outputs (patterns, drawing points). It enumerates the patterns detected and names the sibling chart_analyzer_study for methodology, so an agent can separate it from chart_analyzer_batch and the crypto_* analytic 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?

Gives clear input-mode routing: contract (+ chain when the address alone is ambiguous) OR symbol OR candles, with the conditions for each spelled out. It does not, however, state when to prefer this tool over chart_analyzer_batch or crypto_outlook, so it is context-rich but not exclusionary.

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