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

Beyond the readOnly/openWorld annotations, it discloses pricing ($0.003 USDC via x402, failed calls not charged), a concrete failure mode (HISTORY_TOO_LONG), and a hard blind spot (cannot see Jito bundle metadata). These are exactly the operational traits an annotation cannot express.

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 mechanism is front-loaded in the first sentence, followed by the interpretation, limitations, and pricing in a tight sequence with no filler. It is on the longer side but every clause carries decision-relevant information.

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 complex, paid, open-world on-chain analysis tool, the description covers mechanism, interpretation caveats, failure conditions, and cost. With an output schema present, return-value detail is not required, and nothing an agent needs to decide whether to call it is missing.

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?

There is a single parameter with 100% schema coverage that already documents the mint as a base58 address of 32–44 chars. The description only reconfirms that it operates on a token mint and adds no format or edge-case detail beyond the schema, so 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?

The description states a specific mechanism: inspecting the first Solana slot where a token mint appears and counting distinct fee payers. The resource (token mint), the data source (public RPC), and the output signal (bundle-sniping risk) are all concrete, so an agent can distinguish this from the many token-safety siblings without opening the schema.

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 clear interpretive guidance ('a signal, not proof') and states the operating limits up front (HISTORY_TOO_LONG for long histories, no Jito bundle metadata visibility). It stops short of naming an explicit alternative sibling or a 'use this instead of X when' rule, so it is clear context rather than full when/when-not routing.

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