tenero_whale_trades

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

No annotations, so the description carries the full burden. It does add real context: the upstream API (api.tenero.io) and 'no authentication required.' However it says nothing about rate limits, response shape, pagination, or what threshold defines a 'whale' trade — gaps that matter for an unannotated tool.

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 core sentences are tight and front-loaded. The trailing 'Tip: call earning_opportunities' is promotional filler that does not help an agent decide to call this tool, so not every sentence earns its place.

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?

For a simple two-optional-parameter read tool with no output schema, the description is adequate but thin: it omits what a returned trade contains, the default window ('recent'), and the meaning of 'large/threshold.' It is callable as-is but leaves the agent guessing about results.

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 is 3 — the schema already documents chain, defaults, and the 1–50 limit bound. The description adds no parameter detail and even introduces a 'threshold value' concept that has no corresponding parameter in the schema, which could confuse an agent.

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?

States a specific verb and resource: 'Get recent large/whale trades above threshold value.' The 'whale trades' framing separates it reasonably from tenero_wallet_trades, though it never names that sibling explicitly. Minor tension: the description scopes it to 'the Stacks ecosystem' while the chain parameter also accepts spark and sportsfun.

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?

'Useful for tracking smart money and large market movements' implies a use case but gives no explicit when-to-use/when-not guidance and names no alternative among the many tenero_* siblings. The only explicit pointer is to `earning_opportunities`, which is unrelated to choosing this tool.

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