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

Annotations already establish read-only, open-world, and idempotent behavior. The description adds meaningful context beyond that: the simulated buy-transfer-sell methodology, the signals checked, the free preview vs paid tiers, and the caveat that SAFE is not a guarantee.

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 description is front-loaded with the verdict and score, then moves to methodology, preview/paid tiers, and disclaimers. It is information-dense and mostly earns its length, though the endpoint pricing details could be trimmed if space were a concern.

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-value burden and does so well: it names the verdict, score, flag counts, and the additional reasons/evidence available through paid endpoints. It also discloses limitations, making the tool sufficiently complete for an agent to call it correctly.

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 only one parameter and the schema fully documents it as a Base chain 8453 ERC-20 contract address with an example. The description repeats the chain and token type but adds no syntax or validation details beyond the schema, so baseline 3 is appropriate.

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 resource and operation: a safety verdict for a Base (chain 8453) ERC-20 token. It also names the concrete output categories (SAFE / CAUTION / DANGER, 0-100 score), so an agent can tell exactly what the tool produces.

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?

The description makes the use case clear: checking Base ERC-20 token safety, with a free preview and paid endpoints that add reasons/evidence. It does not name explicit exclusions or alternatives, but there are no sibling tools and the paid-vs-free distinction gives useful selection context.

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