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

With no annotations, the description carries the full burden and does disclose the two notable behavioral traits: monetization (0.02 USDC via x402 PAYMENT-SIGNATURE, auto-paid by capable clients, free for API-key clients) and that output is a ranked list. It stops short of latency, freshness/caching, or whether the ranking metric is exposed.

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?

Front-loaded with the core action sentence, then return shape, then usage triggers, then a bracketed access note. Every sentence carries information, though the payment block is longer than strictly necessary for a tool-selection decision.

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?

No output schema exists, so the description must convey return shape — it does ('ranked list of tokens with high smart-money activity'), which is the essential part. It omits result field detail and any indication of ranking metric or data freshness, which leaves a small gap for a discovery tool.

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 baseline is 3. The description only echoes the schema's intent ('across the specified chains', ranked list) and adds no format hints for timeframe, chain identifiers, or how limit interacts with ranking.

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 specific verb (screen) and resource (tokens ranked by smart-money accumulation/distribution) plus the scope dimension (chains). However, it never distinguishes itself from the many adjacent siblings such as get_smart_money_netflows, get_smart_money_holdings, or screen_candidates, so the agent must infer the boundary itself.

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?

Explicit use cases are given: 'what smart money is currently buying', 'which tokens are being accumulated', 'discover high-conviction smart-money plays'. That is clear positive guidance, but there is no when-not guidance and no named alternative for raw flow/holdings lookups that a sibling already provides.

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