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

With no annotations, the description carries the full burden. It does disclose the output scale (0-100) and the factors contributing to the score, which sets basic expectations for a read-only analysis tool. However, it does not mention input requirements, potential failure modes, or whether the operation has side effects, leaving notable behavioral gaps.

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 a single compact sentence that front-loads the core function and enumerates components efficiently. It wastes a few tokens by repeating the tool name as a prefix, but overall it is appropriately concise.

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?

Without an output schema or annotations, the description omits critical invocation details: whether both chain and token are required, supported chain formats, and what the full response payload looks like. Given two loosely specified parameters and many similar sibling tools, this is insufficient for confident, 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 coverage is 100%, so the baseline is 3. The description does not add any detail beyond the schema's generic 'Chain to process' and 'Token to process', failing to clarify whether token should be an address or symbol or what chain identifiers are accepted. It neither materially improves nor harms parameter understanding.

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 the tool computes a 'Token liquidity health score (0-100)' and lists the contributing metrics (total depth, pool concentration, DEX diversity, holder count). This makes the tool's function recognizable and distinct from generic helpers, though it does not explicitly differentiate it from similar token analytics siblings.

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?

No guidance is given about when to use this tool versus alternatives like x402-token-risk-report, x402-pool-intel, or x402-dex-depth. The agent must infer appropriate usage solely from the name and vague parameter descriptions.

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