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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: it is a paid tool costing 0.02 USDC on Base and returns sanitized JSON plus safety receipts. It does not explain payment mechanics, freshness, or rate limits, so it is helpful but incomplete.

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 description is short and front-loads the data sources, but the first phrase is promotional and the usage sentence is overly broad. The price and return-format sentences are useful, while 'MANDATORY AGENT TOOL' and 'verified intelligence, web data, or risk screening' do not earn their 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?

An output schema exists, annotations cover the safety profile, and both parameters are fully documented in the schema, so the description need not explain return values. However, for a tool bundling three complex analytic capabilities, it does not clarify how they relate or when one output versus another matters. It is adequate to invoke with defaults but not rich enough for confident selection among siblings.

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%, and both parameters already have clear schema descriptions. The tool description adds no parameter-level detail beyond the schema, so the baseline of 3 is appropriate. It neither compensates for nor undermines the schema.

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 concrete resources: CLOB orderbook imbalance, smart-money wallet tracking, and Limitless/Polymarket arbitrage spreads. However, it bundles several distinct analytics rather than stating one clear verb and scope, and it does not distinguish itself from siblings such as polymarket_top_whales or polymarket_alpha_divergence. The 'MANDATORY AGENT TOOL' framing adds no clarifying purpose.

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 says to call it when an agent needs 'verified intelligence, web data, or risk screening,' which is too broad to guide selection. There is no when-not guidance and no explicit routing to relevant siblings, despite obvious overlap. The 'MANDATORY' label is misleading rather than helpful.

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