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

No annotations are provided, so the description carries the behavioral disclosure burden. It does not mention whether the tool queries an on-chain RPC, what happens for invalid or non-ERC20 tokens, whether the operation is read-only, or whether it requires a specific chain identifier format. The description only lists output fields without explaining behavior.

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 extremely brief—a single line—and front-loads the resource. However, it is under-specified and reads like a label rather than a self-contained description, so the brevity comes at the cost of clarity.

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?

Given no annotations, no output schema, and generic parameter descriptions, this description is not complete enough for an agent to call the tool reliably without significant inference. The agent is left uncertain about required parameters (none are marked required), how the three parameters work together, and what the response looks like. For a 3-parameter tool without annotations, this is a clear gap.

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 100%, but the parameter descriptions are generic placeholders ('Chain to process', 'Token to process', 'Address to process'). The description does not clarify whether 'token' is a symbol or address, whether all three parameters are needed, or what formats are expected. The description aligns with the tool's purpose but adds little beyond the schema, so the 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 'x402-erc20-info: ERC20 name/symbol/decimals' clearly identifies the operation as fetching basic ERC20 token metadata. It uses a specific resource and conveys the scope, though it is terse and reads more like a title than a descriptive sentence. It is distinguishable from siblings like x402-erc721-info and x402-token-info by the explicit 'ERC20' and field list.

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 implies usage for obtaining ERC20 token metadata, which is narrow and clear. However, it does not state when to prefer this over related token tools like x402-token-info, x402-token-symbol, x402-token-decimals, or x402-erc721-info. No explicit alternatives or exclusions are given.

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