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

Goes well past the annotations: latest-block semantics, no transaction or gas, 8 KB calldata cap, 422 with revert reason and no charge on failure, and a pricing model ($0.01/call, first 25 free) that explains why idempotentHint is false despite readOnlyHint being true. Read-only and open-world claims in the annotations are reinforced, not repeated.

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 purpose, scope, and usage before the example, limits, and pricing. Dense but nearly every clause carries decision-relevant information; the pricing sentence is multi-clause and slightly crowded, though its content is justified.

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?

No output schema exists, so the description supplies the return shape (raw return data, decode via ABI), the error contract (422 with reason, uncharged), size limits, and cost. An agent has everything needed to call correctly and interpret the result.

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 the baseline is 3, but the description adds real value: an 8 KB limit on data that the schema does not state, a worked to/data pair, and the instruction to decode the raw return with the function's ABI. The optional `from` parameter is left to the schema.

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 (read-only contract call, eth_call) plus the chain, and explicitly scopes it to view functions that have no dedicated tool. That lets an agent pick it over bera_token_balance, bera_storage, or bera_logs without opening any 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 a clear usage rule: use it for any view function that has no dedicated tool, with a concrete example (USDC totalSupply). It signals that dedicated tools are the preferred alternative but doesn't name a specific sibling to fall back to, so it is short of fully explicit routing.

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