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 discloses the exact output shape (one 0-100 safety score + verdict), the scope of analysis per chain family, and the commercial/access model (x402, USDC, $0.01 per call) — genuinely useful context an agent cannot get from structured fields. Gaps remain: no default for the chain parameter, no error behavior for unsupported chains, no latency or rate-limit note.

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?

Front-loaded with the purpose, then a compressed enumeration of what is checked, then the output, disclaimer and price. Nearly every clause carries signal. It is dense but not padded; a slightly cleaner separation of the chain list from the check list would help scanability.

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 2-param tool with no annotations and no output schema, the description covers purpose, chain coverage, analysis scope, return format (score + verdict), cost and disclaimer — everything needed to decide and pay for a call. The missing pieces are the chain default, address format expectations, and differentiation from the near-identical pretrade sibling.

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 0%, so the description must compensate, and it partly does: it enumerates the supported chains (Solana incl. pump.fun, Ethereum, BSC, Base), which effectively defines valid values for the undocumented 'chain' param. But 'address' is never clarified as a token mint/contract rather than a wallet address (a real ambiguity given the solana_wallet_profile sibling), and no format hints (base58 vs 0x) or chain-default behavior are given.

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 and action: a honeypot/rug-pull safety check on a token, across Solana (incl. pump.fun), Ethereum, BSC and Base, returning a 0-100 score plus verdict. That is unmistakably a token-contract safety scan. It does not, however, distinguish itself from the sibling token_pretrade_check or crypto_address_risk, so the agent must infer which one applies.

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?

Usage is implied by the enumerated checks (mint/freeze authority, holder concentration, LP locked, sell simulation) which tell the agent this is a pre-trade token due-diligence call. There is no explicit when-to-use/when-not statement and no routing against the very similar token_pretrade_check sibling. 'Signals, not advice' is a caveat, not usage guidance.

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