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

With no annotations, the description carries the full burden and does well: it reveals that the call does not return the analysis but instead returns exact x402 payment instructions for POST /v1/paid/deep-check, which is a critical non-obvious behavior. It still omits price, whether the call is per-mint billed, and what the agent should expect after payment settles.

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?

Two dense sentences, front-loaded with the value proposition and the returned data set, with the payment caveat placed at the end where it reads as a call-to-action. The parenthetical feature list is long but each item is informative rather than filler.

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 one-parameter, no-output-schema tool, the description covers both the analytic payload and the unusual x402 payment flow, which is the main failure mode an agent could hit. The remaining gaps, cost and post-payment behavior for the mint parameter's expected format, are modest but real.

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 single required parameter 'mint' has 0% schema description coverage, so the schema contributes nothing and the description must compensate. It only implies the token via 'Solana token' and gives no address format, network qualifier, or example, leaving the agent to guess that 'mint' is a base58 mint address.

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 (Solana token) and enumerates exactly what the deep check returns: holder concentration, shared-funder clusters, creator-funded holders, fresh wallets, LP lock/burn, authorities, and a score with reasons. The word 'deep' implies a more thorough counterpart to check_solana_token, but the sibling is never named, so differentiation is left 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?

It discloses the decisive usage fact that this is a PAID endpoint requiring x402 payment, which tells the agent not to call it casually. However, it never states when to prefer it over check_solana_token or batch_check_solana_tokens, nor what prerequisites (funded x402 wallet) are needed before calling.

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