Read contract

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

No annotations are provided, so the description carries the behavioral disclosure burden, and it does identify the operation as read-only and view/pure, which prevents misuse. It also discloses that arguments are coerced by type, which is a useful behavioral detail beyond the schema. It does not mention revert handling or exact return value formatting, but the safety-critical read-only trait is well covered.

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 description is concise and immediately states the tool's purpose in the first sentence. It uses two direct sentences with valuable examples and avoids redundant wording.

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?

The description plus the fully documented schema gives an agent everything needed to construct a valid call: address, function signature, string arguments, and network selection. It does not explicitly describe what happens on reverts or how return values are presented, but the core calling pattern is well covered.

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?

The schema already describes all parameters at 100% coverage, so the baseline is 3. The description adds value by giving concrete signature examples, clarifying the optional 'function' prefix, and explaining that arguments are provided as strings and coerced by type.

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 clearly states the tool calls a read-only view/pure contract function and explains the function is passed as a human-readable ABI signature. It distinguishes itself from sibling read tools by focusing on arbitrary contract function calls rather than pre-defined operations like balance or token info.

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 makes it evident that this is for read-only view/pure functions and gives concrete signature examples, which implies when it should be used. It does not explicitly name alternative sibling tools such as get_balance or get_token_info, but the read-only function-call context is clear enough for an agent to make reasonable routing decisions.

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