get_bigbuys

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds that results are a 'recent' feed of 'large' buys for a single chain, but leaves the threshold defining 'big,' ordering, and result volume undefined.

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?

A single tight sentence with no filler and the key scoping fact (per-chain, recent, large buys) front-loaded. It is efficient, though the brevity leaves real gaps rather than being deliberately minimal.

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?

With no output schema and no annotations covering semantics, the description should explain what qualifies as a 'big buy,' how many records come back, and how ordering works. None of that is present, so an agent cannot predict the result shape or size beyond 'some large recent buys.'

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 only 50%: chainId is documented in the schema (with a Solana example) but `limit` has no description anywhere. The description's 'for a chain' merely restates chainId and says nothing about the limit parameter, its default, or valid range.

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 gives a concrete verb+resource framing ('Big buy' alert feed) and specifies that it returns recent large buy transactions for a chain, so an agent can tell it apart from generic trade-history tools like get_token_trades or get_hl_trade_history. It stops short of naming any sibling explicitly.

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?

There is no statement of when to use this feed versus related siblings such as get_token_trades, get_top_traders, or get_token_details, and no prerequisites or exclusions are given. The agent must infer usage from the one-line purpose alone.

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