get_whales

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

No annotations are provided, so the description carries full burden. It mentions the cost ('40 sats per call') and the type of alerts, but fails to disclose whether the tool is read-only, whether it modifies state, or any prerequisites beyond the L402 mode hinted in parameters. Key behavioral traits are missing.

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 a single sentence followed by a cost note. It is extremely concise, front-loads the core purpose, and every character adds value.

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, the description should explain what the response looks like. It does not mention return format, pagination, or limitations. For a simple listing tool, this is a notable gap.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds minimal value beyond the schema; it mentions L402 mode which is already in the schema. No additional meaning is provided for the parameters.

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 explicitly states what the tool does: 'Recent whale alerts: large transfers, consolidations, distributions in the mempool.' This provides a specific verb-resource combination (get whale alerts) and distinguishes it from sibling tools (which are mostly AI or mempool state tools).

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?

No guidance is given on when to use this tool versus alternatives. The description only explains what it does, not when to invoke it or when to avoid it. Sibling tools are diverse but no explicit comparisons or exclusions are provided.

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