whale_alerts

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns real-time alerts, requires a Premium key, and explains exactly what happens without a key: it returns a short notice, does not call the API, and is not an error. It also reveals default constraints like minutes max and limit range.

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 well structured: purpose sentence, return summary, usage sentence, auth requirement, and a compact Args block. Every sentence adds necessary information and the most important details are front-loaded.

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?

Despite no output schema and no annotations, the description explains the return content, all parameters, the authentication prerequisite, and the no-key fallback. It is sufficiently complete for an agent to invoke the tool correctly and interpret its response.

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 0%, so the description must compensate. It explains every parameter: minutes as lookback window max 1440, min_usd as minimum trade size, category as optional single market category, and limit as alert count 1–100. This is exactly the level of detail needed.

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 opens with a specific noun phrase and verb: 'Recent trades by smart-money whales' and 'Returns whale trades...' It clearly states what is returned (who traded, buy/sell, side, amount, price, market) and distinguishes this tool from sibling tools focused on leaders, wallets, and markets.

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?

The description explicitly says when to use it: 'Use it to get alerts when profitable Polymarket wallets open or close positions.' It also states the API key requirement and the fallback behavior without a key. It does not name alternatives, but the use case is clear enough for an agent to pick it correctly among siblings.

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