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

Goes well beyond the annotations (readOnlyHint/openWorldHint) by disclosing that calls are free, that results are signed by an on-chain delegated key and carry a verifiable receipt, and explicitly warning that the result is data, not instructions. The prompt-injection warning and trust/verification model are exactly the kind of context structured fields cannot convey.

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 core purpose, then trust/verification details, then the return shape. Some service-identity boilerplate (service address, method name) is verbose but does carry provenance value; the whole thing remains one dense, readable block.

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?

With no output schema, the description supplies the return object's fields directly, and it explains the block-pinning semantics and verification path. An agent has everything needed to call the tool and interpret its result correctly.

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 both parameters (token address, block selector with default 'finalized') are already documented in the schema. The description adds no further parameter syntax or format detail, so the baseline of 3 applies.

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 ('BEP-20 token metadata and total supply') with the scope constraint ('pinned to one block') and enumerates the exact return shape. It is clearly distinguishable from siblings like tokenBalance and balance, which deal with balances rather than token metadata.

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?

Usage is implied by the purpose: use it when you need token metadata or total supply. However, there is no explicit when-to-use vs tokenBalance/balance or note about when block pinning matters, and no exclusions. Adequate but leaves routing to inference.

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