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

With no annotations, the description carries full burden. It states it 'submits an ERC-4337 UserOperation', implying a state mutation, but does not disclose what happens after submission (e.g., whether it waits for confirmation, returns a hash, or any side effects). Missing permission requirements, gas costs, or potential reverts.

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 a single sentence with no unnecessary words. It is concise and front-loaded with the action. Could be slightly restructured for clarity (e.g., 'Unstakes a token by submitting an ERC-4337 UserOperation via Fuse's staking module').

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 tool's complexity (3 required parameters, no output schema, no annotations), the description lacks key context. It does not explain the return value (e.g., UserOperation hash), the process flow, or how the receipt token is obtained. The description is too brief to fully inform an agent.

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 detailed parameter descriptions. The tool description adds no additional meaning to the parameters. Baseline score of 3 is appropriate as the schema already documents each parameter's purpose.

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 tool submits an ERC-4337 UserOperation to unstake a token via Fuse's staking module. It uses a specific verb ('unstakes') and resource ('token'), distinguishing it from the sibling stake tool. However, it could be more explicit about the outcome (e.g., returning tokens to wallet).

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?

No guidance on when to use this tool vs. alternatives (e.g., when to unstake vs. stake). It does not mention prerequisites like needing a receipt token address from fuse_get_staking_options, though that is hinted in a parameter description. The description itself provides no usage direction.

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