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

With no annotations, the description carries the behavioral burden and does an adequate job: 'INFORMATION ONLY' signals read-only behavior, and the x402 pricing discloses cost, currency, and network. It doesn't cover authentication or rate limits, but the main side effect and cost are explicitly surfaced.

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?

The entire description is one packed line with no filler: purpose, input, read-only nature, and pricing are all present. Key facts are front-loaded, and every segment earns its place.

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-parameter, no-output-schema tool, the description covers input and cost and sketches the return (market-vs-narrative signal, fear/greed). It falls short on output shape or example values and uses jargon like 'OSINT' and 'x402' without explanation, so an agent may still be unsure of exact call semantics.

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 schema only says 'service input,' while the description narrows the single parameter to an asset, which is meaningful semantic information. It could be more precise (e.g., ticker format), but it adds value beyond the generic schema description.

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 states that the tool provides a condensed market-vs-narrative signal plus fear/greed for a given asset, which is a specific deliverable. It lacks an explicit verb and does not name sibling tools like trading-signal or sentiment, so it doesn't fully distinguish itself, but the resource and scope are identifiable.

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 clearly tells the agent the usage context: provide an asset as input, expect information only, and note that the call costs 5.0 USDC on Base via x402. It does not mention alternatives or when not to use it, but for a single-input information tool the context is adequate.

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