fomo_add_watchlist

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

No annotations are provided, so the description must carry the full behavioral burden. It only says 'Add a token' and does not disclose idempotency, duplicate handling, authorization requirements, or side effects. This is a mutation tool with no additional behavioral transparency.

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 single sentence is brief but not truly concise – it omits essential context while adding no fluff. This is under-specification rather than efficient summarization, so it does not fully earn 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 an action tool with two required parameters and no output schema, the description provides minimal guidance. It does not indicate the return value, success or failure conditions, or any additional expectations, leaving the agent without enough information to handle the tool's outcome 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 0%, and the description makes no attempt to explain 'tokenAddress' or 'networkId'. The phrase 'Add a token' only vaguely maps to 'tokenAddress', and the required 'networkId' is entirely omitted. The description fails to provide any meaning beyond the schema's type declarations.

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 states a specific verb ('Add') and resource ('token to the watchlist'), which distinguishes it from fomo_remove_watchlist and fomo_get_watchlist. However, it does not specify whose watchlist or that it targets the current user's watchlist, which creates slight ambiguity.

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 is provided on when to use this tool versus its siblings, such as fomo_remove_watchlist or fomo_get_watchlist. There is no mention of the operation or context, so an agent cannot determine the right choice based on this description alone.

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