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

With no annotations, the description carries the full burden and does substantial work: it discloses that the call costs $0.01 USDC, that output includes rule-based risk flags plus a score and verdict, and adds a 'not financial advice' disclaimer. It omits failure semantics (e.g., whether the fee is charged on an invalid address or unsupported chain) and does not explicitly state the call is read-only/no state change.

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 core capability list is front-loaded in the opening clause, with pricing and disclaimer trailing. It is efficient for the amount of information packed in, though the long comma-spliced enumeration reads as a run-on and could be broken into two tighter sentences.

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 correctly takes on the job of describing return content (risk flags, 0-100 score, verdict, DEX metrics), which is the main thing an agent needs. The remaining gap is the undocumented multi-chain parameter and default behavior, which matters for correct invocation.

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 largely does not. The required `address` is inferable from 'ERC20 token', but the `chain` parameter — an enum of base/ethereum/arbitrum/optimism/polygon — is never mentioned, and no default chain is stated, so an agent cannot tell what happens if it omits it or which chains are actually supported for DEX metrics.

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 concrete analysis resource (ERC20 token risk) and enumerates exactly what is checked: name/symbol/supply, owner renouncement, upgradeable proxy, DEX price/liquidity/volume/pair age, plus a 0-100 score and verdict. This clearly separates it from siblings like token_metadata (static metadata) and token_allowance.

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?

"Use this before buying, accepting or listing an ERC20 token" gives an explicit usage trigger tied to real decisions. It does not name an alternative tool or state when not to use it, so it stops short of full routing guidance, but the context is unambiguous.

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