get_bigbuys

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

No annotations are provided, so the description carries the full behavioral burden. It conveys only that this is a recent-activity read feed; it says nothing about how 'large' is thresholded, result ordering, pagination, rate limits, or auth requirements, all of which matter for interpreting a 'big buy' alert.

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 front-loaded sentence that defines the resource and its scope with zero filler. Nothing is repeated or wasted.

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-parameter read tool with no output schema, the definition is minimally viable but thin: with no annotations and no output schema, an agent still cannot tell what the threshold for a 'big buy' is, how results are ordered, or what limit does. The essentials for selection are present; the essentials for correct interpretation are not.

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 only 50%: chainId is documented in the schema with an example, but 'limit' has no description anywhere. The description mentions neither parameter, so it fails to compensate for the undocumented limit or to clarify what limit controls (count vs. lookback window).

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 names a specific resource ('Big buy alert feed') and its content ('recent large buy transactions'), scoped to a chain, so an agent can distinguish it from generic read tools like get_trade_history or get_token_trades. However, it never names a sibling or clarifies the boundary with token-level trade feeds, leaving differentiation to inference.

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 get_token_trades, get_trade_history, or get_trending_tokens, and no prerequisites or exclusions. The agent is left to infer that this is for surfacing whale/large-buy activity on a specific chain.

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