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

Annotations already declare this a read-only, idempotent, non-destructive open-world call, so the safety bar is met. The description adds genuine behavioral value by disclosing the verdict taxonomy the agent must interpret and the exact factors that roll into it, which no structured field conveys. It stops short of describing response shape or whether per-signal detail accompanies the verdict.

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?

It is a single sentence with a front-loaded purpose clause, waste-free despite the dense signal list. Readability would improve slightly if the verdict options were split out from the colon-delimited enumeration, but no sentence is 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?

With no output schema, the description carries the burden of explaining returns and does so by naming the three verdict values. What remains unstated is whether the underlying signals are returned alongside the verdict or only the grade, which matters for how an agent should report results to a user.

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 at 100% schema description coverage, and the schema already explains the base58 mint address and the 'high' suffix convention for higher.fun mints. The description adds no additional parameter meaning, so the baseline of 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 names a specific analysis action on a specific resource (a coin's mint) and enumerates the concrete signals inspected: mint/freeze authority, holder concentration, snipers, bundled wallets, dev selling, ticker flags. It also states the output taxonomy (CLEAN_ON_CHECKS / CAUTION / HIGH_RISK), which clearly separates it from data-retrieval siblings like get_coin or get_coin_holders.

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?

"Safety check before anyone trades a coin" establishes a clear usage context tied to the trade flow (build_trade, quote_trade). However, it never names an alternative or states when not to use it — e.g. that it is not a substitute for get_coin metadata or check_ticker — so guidance is contextual rather than explicit.

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