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

Annotations already cover read-only/idempotent/openWorld, and the description still adds material behavior the agent cannot get elsewhere: pricing ($0.04/call via x402 on Base), the prepaid x-credit-token header for unlimited calls, the absence of a free tier, and no API key requirement. That is exactly the kind of billing/auth context a caller needs before invoking.

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 well with the core question, but it restates the required input twice ('wallet= required' and 'Required input: wallet') and packs disclaimers and pricing into the same breath as semantics. The redundancy and mixed concerns cost it efficiency.

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?

With an output schema present, the description needn't explain return values, and it covers everything else an agent needs: what is measured, the default and max lookback, cost, auth header, and the interpretive meaning of the result.

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 the baseline is 3, but the description adds meaning the schema lacks: the default lookback (30 days) and the hard cap (max 90), which the schema only calls 'Lookback days (optional)'. Wallet is confirmed as required in both.

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?

Opens with a precise question ('Is this wallet's USDC freshly bridged, and from where?') and names the mechanism ('Cross-chain inflow detection', 'correlates recent USDC MINTS with Circle CCTP receives'). It explicitly distinguishes the output ('freshly bridged in ... vs natively issued') and claims no sibling surfaces it, so an agent can separate it from bridge_status/bridge_route without opening schemas.

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?

Gives clear context for use ('a real signal for trading and liquidation agents') and explains what the result means, but names no alternative tool and states no explicit when-not condition. The sibling set contains plausible overlaps (bridge_status, bridge_route, wallet_activity) that are never addressed.

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