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

With no annotations, the description carries the whole behavioral burden and does a good job: it discloses the data source (DexScreener), the static (non-live) nature of the read, the supported chains (Base/Polygon), the output shape (0-100 score, pair count, liquidity depth), and the per-call cost ($0.010 USDC). It stops short of describing auth/payment flow, error behavior for unknown tokens, or rate limits.

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?

One front-loaded sentence that leads with the purpose, then the scope, then the outputs, then the price. Nothing is wasted, though the stacked parentheticals make the middle slightly dense.

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?

The enumerated output fields partially compensate for the absent output schema, and pricing is disclosed. However, the tool takes only an 'address' yet claims Base/Polygon coverage with no chain parameter, leaving unclear how the chain is determined — a real gap for a one-parameter tool with no annotations and no output schema.

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% on the single 'address' property, so the description must compensate. It implicitly tells the agent this is an EVM token contract address (not a wallet or Solana address) by scoping to 'an ERC-20 on Base/Polygon', but gives no format, checksum, or validation guidance.

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?

Names a specific verb+resource and scope: a static risk read for an ERC-20 token on Base/Polygon, and even enumerates the outputs (liquidity depth, pair count, 0-100 score). The 'EVM' qualifier cleanly separates it from solana_risk_check, but it does not distinguish itself from risk_check or trust_check, which are plausible alternatives.

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?

'Static risk read' implies a point-in-time snapshot rather than continuous monitoring, which is useful context, but there is no explicit when-to-use framing, no statement of when to prefer trust_check/risk_check/token_report instead, and no prerequisites for calling it.

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