chainpeek: an ERC-1155 token balance on Ethereum, Base or Robinhood Chain

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

Goes well past the annotations: discloses an ERC-165/balanceOf capability check, the specific 422 `not_erc1155` failure mode and that it is not charged, 30 s RPC caching, typical sub-second latency, USD 0.001 pricing and a 10-reads/IP/day free tier. Annotations only supply the safety profile, so this added operational context is genuinely valuable.

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?

Purpose and the sibling routing are front-loaded, and the dense sentence carries pricing, caching and error semantics efficiently. It repeats the 422/not-charged idea twice and the chain list twice ('Ethereum, Base or Robinhood' appears in both title and body), which is minor redundancy rather than bloat.

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 single-value read with four required params, the definition covers return shape (balance raw integer string, is_erc1155 flag, block), the failure taxonomy, cost model and latency. With an output schema present, nothing an agent needs before calling is left unstated.

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% with patterns and an enum already documented, so the baseline is 3. The description adds little parameter detail beyond echoing that balanceOf takes (account, id); it does not explain token_id encoding or address normalization beyond what the schema states.

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 and resource (get ERC-1155 token balance for a token id) and pins the scope to three named chains. It explicitly routes the adjacent case away ('For an ERC-721 owner use get_nft_owner'), so an agent can separate it from sibling token-read tools without opening the 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?

Gives an explicit alternative and the condition that selects it (ERC-721 owners go to get_nft_owner), plus the chain restriction. It does not contrast against other balance-ish siblings (get_balance, get_token_info, get_nft), so guidance is clear but not exhaustive.

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