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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds real value beyond them: the data source ('from our snapshots'), the time windows, and pricing (0.030 USDC per call, included in subscriptions). It omits any note on rate limits or freshness of snapshots.

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 leads with the usage condition and packs the return content efficiently. Slightly dense but nothing is wasted; the pricing clause is appended cleanly.

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, the description carries the return-shape burden and does so reasonably by enumerating new/exited holders, concentration shift and large-holder selling. Combined with read-only annotations and full param coverage, it is nearly complete, though exact metric definitions remain unspecified.

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?

Only one parameter (mint) and schema description coverage is 100%, so the schema already documents it. The description implies the token context but adds no format or constraint detail beyond the schema. Baseline 3 applies.

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 resource (top holder changes for a Solana token) and scope (1h and 24h windows, new/exited holders, concentration shift, large holders selling). An agent knows exactly what analysis this produces, though it does not explicitly distinguish itself from sibling token_deep_check.

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?

Opens with an explicit use-case framing ('Use to see whether insiders are leaving a Solana token'), giving clear context for selection. It does not name alternatives or say when NOT to use it versus token_deep_check or market_snapshot, so it falls short of a 5.

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