fomo_search_clans

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Search clans by term,' which implicitly suggests a read operation but offers no details about return format, pagination, rate limits, or potential side effects. This is a critical gap for a tool with zero annotation coverage.

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, terse sentence with no redundancy, achieving conciseness and front-loading the action and resource. While it is structurally tight, the brevity results in under-specification, but that is more a content completeness issue than a conciseness flaw.

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 one required parameter and no output schema or annotations, the description must at least indicate the return type (e.g., a list of clan summaries) and any constraints. This description provides none, so an agent cannot reliably know what to expect when invoking the tool.

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?

The schema has zero description coverage, and the description adds no information about the 'searchTerm' parameter beyond the word 'term.' It does not explain matching rules (e.g., exact vs. partial), case sensitivity, wildcard support, or any accepted formats. The agent is left entirely to infer from the parameter name.

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 uses the verb 'search' and the resource 'clans,' clearly stating the tool's core action. However, it does not differentiate this from sibling search tools like fomo_search_users or fomo_search_tokens beyond the resource name, leaving some ambiguity in a list with many similar search alternatives.

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 alternatives such as fomo_get_clan, fomo_get_clan_leaderboard, or fomo_search_users. There is no mention of search scope, result type, or conditions that would make this tool preferable over others.

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