get_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 of behavioral disclosure. It mentions 'real-time' and 'alerts,' implying timely notifications, but lacks details on rate limits, authentication needs, data freshness, or whether this is a read-only operation. The 'Price: $0.35' hints at a paid service but doesn't clarify billing conditions.

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 and front-loaded with the core purpose, followed by parameter explanations and return details. Every sentence earns its place, with no redundant information. The 'Price' line is concise and relevant for cost-aware usage.

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 the tool's moderate complexity (2 parameters, no annotations, but with an output schema), the description is partially complete. It covers parameters and return value basics, but lacks behavioral context like rate limits or real-time constraints. The output schema existence reduces the need to detail return values, but more operational guidance would help.

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 effectively explains both parameters: 'chains' as 'List of chains to monitor' with a default, and 'min_value_usd' as 'Minimum transaction value in USD to alert on' with an implied threshold. This adds crucial meaning beyond the bare 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 the tool's purpose: 'Get real-time whale transaction alerts across chains.' It specifies the verb ('Get'), resource ('whale transaction alerts'), and scope ('across chains'). However, it doesn't explicitly differentiate from sibling tools like 'detect_fraud' or 'get_trade_signals' that might also involve transaction monitoring.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'detect_fraud' for suspicious activity or 'get_trade_signals' for trading insights, nor does it specify prerequisites or exclusions for usage.

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