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

Describes the read-only nature (view/pure) and the auto-fetching behavior for ABI. Lacks details on error handling if ABI not found or network failures, but covers key behavioral aspects.

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?

Two efficient sentences with no redundancy, front-loading the core purpose.

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?

Sufficient for a read tool; lacks mention of return values but this is often implicit for view functions. No output schema exists, so description could slightly expand on expected output.

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?

Adds meaningful context for the 'abi' parameter (optional, auto-fetched), which is beyond the schema description. Other parameters are straightforward and schema covers them.

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 it calls view/pure functions on Fuse contracts, with auto-fetched ABI. It distinguishes from write actions and other read tools.

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 for custom view/pure function calls, but no explicit guidance on when to use versus alternative read tools or when not to use.

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