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

No annotations provided, so description carries full burden. It discloses state-mutation, server signer usage, auto-ABI fetch, and return of transaction hash. However, it omits important traits like gas estimation, potential failure modes, signer fund requirements, or reversibility. This is insufficient for a mutation tool.

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 two sentences, with the core action front-loaded and a secondary detail about ABI fetching. No wasted words; every sentence is informative.

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?

Given 5 parameters all described, no output schema, and sibling tools, the description covers the core purpose and return value. However, it lacks explicit differentiation from smart wallet write tools (fuse_smart_call_contract) which could cause confusion. Mostly complete.

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% with all parameters described. The description adds value by explaining the optional ABI override behavior ('If omitted, the verified ABI is fetched from the Fuse explorer'). This goes beyond the schema but does not address all parameters in depth, maintaining baseline 3.

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 'Signs and submits a state-mutating contract call from the server's signer.' This distinguishes it from read-only tools like fuse_read_contract and other write tools like fuse_send_erc20.

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 context is implied (state-mutating calls) but no explicit guidance on when to use this tool versus alternatives like fuse_smart_call_contract or fuse_send_native. No exclusions or when-not-to-use are mentioned.

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