fomo_search_tokens

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'search tokens by phrase' without revealing whether the search is case-insensitive, returns partial matches, or has a limit on results. An agent cannot anticipate response size or matching behavior.

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 minimally sized and front-loaded; the single sentence conveys the core action with no filler. However, it could be more informative without much added length, so it is concise but not under-specified enough to be penalized heavily.

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 lack of annotations and output schema, the description is incomplete. It fails to clarify the search semantics, potential result structure, or any usage constraints. An agent may struggle to interpret the response or to form an effective query.

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 for the single parameter 'phrase'. The description only repeats the parameter's name without adding semantics (e.g., format, length limits, example values). It does not clarify whether 'phrase' should be a token symbol or a natural-language phrase.

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 clear verb and resource: 'Search tokens by phrase'. It distinguishes from 'fomo_search_users' and 'fomo_search_clans', which search other entities, but there is no mention of the result scope or filtering; it is generic but not misleading.

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 versus alternatives like 'fomo_filter_tokens' or 'fomo_search_users'. It does not specify what kind of phrase is expected (e.g., exact token name, symbol, partial match) or whether to prefer another tool for broader search.

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