fuse_resolve_ensResolves an ENS name to its EVM address. ENS is not deployed on Fuse — resolution requires ENS_RPC_URL to be configured (typically pointing at Ethereum mainnet). Plain hex addresses are passed through.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ENS name to resolve (e.g. `vitalik.eth`). Plain addresses are returned unchanged. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that ENS resolution depends on Ethereum mainnet access via a configurable RPC URL, and that plain addresses are returned unchanged. This reveals key behaviors beyond the basic action.
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, front-loaded with main action, followed by essential context. No wasted words. Every sentence earns its place.
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 simple resolution tool with one parameter and no output schema, the description covers the key aspects: action, prerequisite (ENS_RPC_URL), and edge case (pass-through). Could mention return format, but it's implied.
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 a good parameter description. The description adds minimal extra meaning beyond the schema, noting that plain addresses are passed through. This meets the baseline but does not significantly enhance understanding.
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?
Description clearly states 'Resolves an ENS name to its EVM address', using a specific verb and resource. It distinguishes from all sibling tools (none are for ENS resolution), making the purpose unambiguous.
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?
Provides explicit context: ENS not deployed on Fuse, requires external ENS_RPC_URL configuration, and plain hex addresses pass through. While it doesn't explicitly state when not to use the tool, this information sufficiently guides the agent on appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes (e.g., balances, trades, staking, notifications), but there is some overlap, such as multiple trading quote tools and parallel EOA vs. smart wallet operations (e.g., send_erc20 vs smart_transfer_token). Descriptions generally clarify differences, so only minor confusion is possible.
All tools follow a consistent `fuse_<verb>_<noun>` pattern (e.g., `fuse_get_balance`, `fuse_send_native`). The notification sub-group uses `fuse_notification_<verb>_<noun>`, which is internally consistent. No mixed conventions or chaotic naming exist.
With 50 tools, the surface is very large and likely overwhelming for agents. Many tools could be combined (e.g., price history and change tools, or multiple notification CRUD tools). The count is excessive for the server's scope, reducing coherence.
The tool set covers a wide range of Fuse operations: token info, balances, staking, trading, ERC-4337 smart wallets, notifications, and contract interaction. The `fuse_explorer_query` tool provides a catch-all for additional explorer endpoints, filling most gaps. Minor missing explicit tools (e.g., block details) are mitigable.