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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds real value beyond that: it is 'free and always answers,' requires no paid membership, and returns only what a non-member 'may see,' implying tiered/limited output. That access-model context is useful and not present in the structured fields.

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?

Three sentences, but the opening is dense and mixes a product pitch ('What Basis Founders adds to this connection') with the actual function. The membership-marketing framing competes with the functional content, so the front-loading is weaker than it could be even though no sentence is redundant.

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 zero params and no output schema, the description does the necessary work of naming what the return contains (tracked whale counts, combined book, top coin) and when to call it. Coverage is adequate for a no-argument preview tool, though it leaves the exact shape of the returned totals implicit.

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?

The tool takes zero parameters, so the schema is empty and the baseline is 4. The description correctly implies a no-argument call whose output is a fixed preview payload, and adds nothing misleading about inputs.

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 states what the tool surfaces (screened Hyperliquid whale counts, their combined book, the coin most hold) and frames it as a founders-membership preview, but it never gives a clean verb+resource statement of the action and blurs purpose with marketing copy. It only loosely differentiates from the hyperliquid_whale_read sibling, relying on a routing sentence rather than a clear 'this tool does X' claim.

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?

It gives explicit triggering conditions ('whale positions, whale or gamma levels, more than 30 days of derivatives history, or a stock or commodity on Hyperliquid or Binance'), which is strong when-to-use guidance. However it names no alternatives and offers no when-not-to-use exclusion, so an agent is not told which sibling to prefer for overlapping whale queries.

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