fomo_remove_watchlist

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The description only states a mutation occurs, but does not explain side effects, whether removal is reversible, auth requirements, or handling of already-absent tokens.

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 one succinct sentence with no redundant words. It immediately conveys the action and target, making it easily scannable for an agent.

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 tool with two required parameters and no output schema, the description omits critical operational details: what networkId indicates, the expected response format, error conditions, and whether the token must already exist in the watchlist. This leaves an agent guessing about correct invocation.

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 0%, so the description must compensate. It interprets token as 'token from the watchlist' but does not explain the role of networkId or clarify that tokenAddress is the token identifier. The description adds minimal value over the parameter property names.

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 tool description states a specific verb ('Remove') and resource ('token from the watchlist'). This clearly distinguishes it from sibling tools like fomo_add_watchlist and fomo_get_watchlist through the verb and direction of operation.

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 provides no guidance on when to call this tool versus its siblings (add/get watchlist). It lacks context on prerequisites, expected state (e.g., token being currently watched), or trade-offs with alternatives.

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