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 things an agent most needs: the data source (Alchemy) and the paid x402 model ($0.030 USDC on Base per call), which is a real gating fact before invocation. It omits alert freshness/latency semantics (real-time stream vs historical scan) and any rate or pagination behavior.

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?

Three short sentences, each load-bearing: what it returns, how to widen the scope, what it costs. The scoping instruction is front-loaded before the payment note, so the most actionable line lands first.

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, and the description does name the returned fields (tx hashes, timestamps), which is the main gap it needed to close. Remaining gaps are the freshness/recency semantics of an alert feed and how limit interacts with the default threshold, neither of which is stated anywhere.

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 only 50% (chain and address described; limit and min_usd not), so the description must compensate. It does so meaningfully for address, clarifying that omitting it switches to a chain-wide scan rather than returning nothing, which the schema's 'Optional wallet to watch' does not convey.

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?

Names a specific resource ('large-transfer / accumulation alerts') and discloses the payload ('tx hashes + timestamps') plus the data source (Alchemy). No sibling covers the same ground, so an agent can route here without opening a schema.

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?

'Omit address for a chain-wide scan' gives explicit conditional usage for the two operating modes of this tool. It stops short of naming alternatives or stating when not to use it (e.g. versus cortex_tx_history or cortex_wallet_intel for address-scoped lookups).

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