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

No annotations are provided, so the description carries the full burden. It discloses that the tool signs and submits calls from the server's signer, auto-fetches ABI, and returns a transaction hash. However, it does not mention permissions required, reversibility, or error conditions, which are important 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?

Two sentences with no wasted words. The first sentence provides the core purpose, and the second adds important details (ABI auto-fetch, return value). Efficiently structured.

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?

For a write tool with 5 parameters and no output schema, the description covers the return value, ABI behavior, and mutation context. It could mention that the call originates from the server's signer and clarify error handling, but overall it provides sufficient information for an agent to use the tool 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 description coverage is 100%, so the schema already documents all parameters. The description adds minimal extra context: that ABI is auto-fetched when omitted and that valueWei is for payable functions. This is adequate but not exceptional.

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 verb ('signs and submits'), resource ('state-mutating contract call'), and key behaviors (auto-fetch ABI, returns transaction hash). It distinguishes from sibling tools like fuse_read_contract by specifying state-mutating nature.

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 implies usage for writing to contracts by stating 'state-mutating contract call' and mentions auto-fetching ABI. However, it does not explicitly state when not to use it or provide alternatives, though the sibling list includes read and deploy tools that naturally differentiate.

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