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 states the tool lists tokens with enriched metadata, implying a read-only operation. However, it does not discuss potential side effects, authentication requirements, or rate limits. The description adds context about the Fusebox metadata but could be more explicit about being read-only and safe.

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 effectively convey the tool's purpose and technology. Every sentence adds value without repetition or unnecessary details. The structure is front-loaded with the core functionality.

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 the low complexity (single parameter, listing operation) and no output schema, the description adequately explains what the tool returns (token list with symbol, decimals, USD value). It is complete enough for an agent to make an informed decision, though it could explicitly state the output format (e.g., array).

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 clear description for the single parameter 'walletAddress'. The description does not add additional parameter-level detail beyond what the schema already provides, so it meets the baseline without adding extra value.

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 that the tool lists all ERC-20 tokens held by a wallet on Fuse, enriched with metadata. This distinguishes it from siblings like 'fuse_get_balance' (single token) and 'fuse_list_supported_tokens' (all supported tokens, not held). The verb 'lists' and resource 'ERC-20 tokens held by a wallet' are specific.

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 when a full portfolio of ERC-20 tokens with enriched metadata is needed, but it does not explicitly state when not to use it or compare with alternatives like 'fuse_get_balance' for a single token. No exclusions are provided, leaving the agent to infer context from sibling tool names.

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