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 return content (who traded, buy/sell, amount, etc.) and the non-error behavior without a key. However, it lacks details on rate limits, caching, or real-time latency, leaving some behavioral aspects implicit.

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 concise and well-structured: a one-line summary followed by a return value list and an Args section. Every sentence adds value without redundancy.

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?

Given no output schema and four parameters, the description adequately explains inputs, Premium requirement, and return fields. It lacks explicit output structure details but lists the fields returned, which is sufficient for a feed tool.

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%, but the description adds comprehensive meaning to all four parameters: minutes (lookback window, max 1440), min_usd (minimum trade size), category (restrict or None), limit (1-100). This fully compensates for the lack of schema descriptions.

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 the tool returns 'Recent trades by smart-money whales' as a 'live alerts feed (Premium)', specifying the verb 'returns' and the resource 'whale trades'. It distinguishes from siblings by emphasizing its real-time nature and Premium requirement, making the purpose unambiguous.

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 states the requirement for a Premium API key via ORCALAYER_API_KEY and describes the behavior without a key (returns a notice). It provides clear context for when to use the tool, though it does not explicitly mention when not to use or suggest alternative tools among siblings.

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