whale_swaps

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

No annotations are present, so the description carries full burden. It discloses payment model (402 if unpaid), result fields, and usdValue calculation. Could add rate limits or auth details, but current info is solid.

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?

One well-structured paragraph: purpose first, then parameter list, then result fields, then payment note. Every sentence adds value, no fluff.

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?

Covers result content (pool, token, quote, USD size, direction, block, age, txHash) and usdValue computation. Lacks default ordering or sorting details, but complete enough for a fetch tool with no output schema.

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 baseline 3. Description adds defaults (min=10000, limit=50) and clarifies direction refers to 'non-quote token', providing value beyond 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 clearly states it returns 'recent large DEX Swap events' for whale-following/copy-trading, specifying DEXs (Uniswap V3 + Aerodrome) and chain (Base). It uniquely identifies the tool's function among siblings.

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?

Provides usage context (whale-following signal), parameter hints (POST with filter options), and payment requirement ('PAID x402 service'). No explicit when-not or alternatives, but sufficient implied usage.

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