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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the read mechanism (eth_call), the supported chains, the returned fields, and the billing model (5 free trial calls per signed wallet). However, it says nothing about failure behavior for non-ERC721 contracts, rate limits beyond the trial, or whether the call is gas-free, leaving meaningful 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 core purpose is front-loaded in a single dense sentence, followed only by a short pricing note. Every clause earns its place; the only slight clutter is the emoji-flagged trial line, which is still informative.

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?

For a 3-parameter read tool with no annotations and no output schema, the description does cover the return values and the execution mechanism, which is the right call. But it leaves the input parameters ambiguous and omits error/edge behavior, so it is only minimally sufficient 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% across three parameters, so the description must compensate and largely does not. It clarifies that 'chain' accepts Base or Ethereum, but never explains what 'token' means versus 'address' — two overlapping-looking parameters that an agent could easily confuse — nor which are required (0 are marked required).

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 verb (Reads), resource (ERC721 contract name and symbol), the mechanism (eth_call on Base or Ethereum), and the exact return fields (address, chain, name, symbol). The ERC721 token standard distinguishes it from sibling tools like x402-erc20-info and x402-erc1155-info without the agent needing to open either schema.

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 constrains the supported chains (Base or Ethereum) but gives no explicit when-to-use guidance and never names the obvious alternatives (x402-erc20-info, x402-erc1155-info, x402-nft-metadata). The '5 free trial calls' line is pricing, not usage guidance, so the agent must infer routing from the name alone.

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