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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds genuinely non-obvious behavior: sub-minute latency, degraded results in thin markets, and a paid 0.55 USDC x402 invocation with a stated payee. That payment detail is essential for an agent to invoke it successfully. It loses a point because the fee-subsidy and identity-verification block is closer to promotion than operational context.

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?

It is well front-loaded: capability, input example, constraints, then commercial terms. But a sizeable share of the text is the 10% fee disclosure, token contract address, and dual-agent identity verification with two URLs and a payout wallet — none of which helps an agent select or 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?

With no output schema, the description correctly carries the burden by enumerating the analytic outputs an agent will receive, and it discloses cost and the payment channel needed to execute. What is missing is any sense of response shape or handling of partial data beyond the thin-market warning.

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 description coverage is 100%, so the schema already documents all three parameters, and the enum supplies the timeframe values. The description's contribution is a concrete invocation example — useful but marginal, and the listed timeframes merely repeat the enum. 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?

The description names a concrete resource and enumerates exactly what is returned: trend, support/resistance, RSI, MACD, moving averages, volume and a bias summary. That is far more informative than the title. It does not, however, explicitly distinguish itself from close siblings like token_due_diligence or contract_research, so an agent must infer the boundary.

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?

It scopes usage by exclusion — 'Indicators only (no order-book or on-chain flow)' — which tells the agent when this tool is the wrong pick, plus a data-quality caveat for thin markets. It stops short of naming the sibling tool to use instead when those inputs are required.

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