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

With no annotations, the description carries the burden and does well: it discloses the data source (smart-money wallet net flows), the categorical output, and the access model — 0.02 USDC via x402 PAYMENT-SIGNATURE header or API key, with auto-pay for capable clients. It stops short of noteable operational details such as rate limits, latency, or behavior on unsupported chains/symbols.

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 return values come first, the disambiguation against the social-sentiment sibling follows, and the access/payment block is confined to a final bracketed note. No filler sentences.

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?

There is no output schema, but the description compensates by naming the label set and the flow-direction field. Access and payment mechanics are covered, so an agent can invoke it correctly; only edge-case behavior (unknown symbol, non-default chain effects) is left unstated.

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 both the symbol and chain parameters (including the ethereum default) are already documented. The description reinforces that the subject is a token symbol but adds no new semantics such as accepted symbol formats or chain-specific limitations, so the baseline 3 applies.

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 gives a specific verb and resource: an on-chain sentiment read derived from smart-money wallet net flows, plus the exact return shape (bullish/bearish/neutral label and net USD flow direction). It is clearly distinguishable from the flow-level siblings like get_smart_money_netflows and from get_social_sentiment.

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 states the triggering user question ('what smart-money sentiment is for an asset') and explicitly routes social-media sentiment requests to get_social_sentiment. Both the when-to-use and the when-to-use-something-else conditions are spelled out.

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