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

With no annotations, the description does add real value by disclosing the mechanism (eth_call, i.e. a read-only on-chain call) and the price ($0.001 USDC), which an agent needs for cost-aware planning. It stops short of stating the return type, behavior for nonexistent contracts/tokens, or whether any auth/API key is required.

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?

Front-loaded with the definition, then mechanism, then a concrete example, then price — every sentence earns its place. The dense inline example is slightly harder to parse than a clean parameter list, which keeps it from a 5.

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 5-parameter, 0%-coverage tool with no annotations and no output schema, the description covers the core call and cost but leaves the wallet/address ambiguity and the return value unexplained. Adequate to invoke, incomplete for confident use.

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 5 parameters, so the description must carry the load; the example does clarify the three required fields plus chain. However it never explains the 'wallet' parameter or how it differs from 'address', and gives no default for 'chain' or format hints for token_id.

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?

States a specific verb+resource ('how many copies of token_id a wallet holds') and names the exact contract method balanceOf(address,uint256), which unambiguously separates it from chain_erc20_balance and chain_erc721_tokens by token standard.

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 example payload implies the intended call shape and the ERC1155 framing implies when to pick this over the ERC20/ERC721 siblings, but no explicit when-to-use or when-not-to-use rule is stated, and no alternative tool is named.

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