fomo_verified_tokens

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

No annotations are present, so the description bears full responsibility for disclosing behavior. 'Verified token list' conveys only that some list is retrievable; it says nothing about filtering, sorting, pagination, authorization, or what 'verified' means.

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 bare noun phrase that essentially restates the tool name (

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?

A zero-parameter tool with no annotations and no output schema needs the description to explain what is returned and how this differs from siblings like fomo_token_feed, fomo_token_allow_list, or fomo_filter_tokens. The two-word description provides none of this.

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?

There are zero parameters, so there is nothing the description must explain beyond the schema. The baseline of 4 applies. However, the description still doesn't explain the shape of the returned list, which slightly reduces its 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 is a noun phrase ('Verified token list') that essentially restates the tool name without specifying an action. It implies retrieval of a list but does not use a clear verb or define the resource precisely. It also fails to distinguish this from several token-related siblings like fomo_filter_tokens, fomo_search_tokens, fomo_token_feed, or fomo_token_allow_list.

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 given on when to use this tool versus alternatives such as fomo_token_feed, fomo_token_allow_list, or fomo_search_tokens. There is no mention of whether this returns all verified tokens, a paginated list, or how it differs from similar tools.

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