fomo_search_users

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

The term 'fuzzy-search' discloses inexact-match behavior, which is a meaningful behavioral trait. However, with no annotations, the description carries the full burden and still omits output shape, result limits, and whether matching is by handle, display name, or other fields.

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 compact phrase with no filler and the key verb is front-loaded. Every word earns 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 a single-parameter search tool, the description is almost sufficient, but it lacks any indication of the expected return value, pagination, or match scope. Without an output schema, the agent must guess what a successful search result looks like.

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 only says 'by term', which adds minimal meaning beyond the property name 'searchTerm'. It does not explain format, length requirements, case sensitivity, or which user fields are searched.

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 names a specific verb, 'Fuzzy-search', a specific resource, 'users', and the input, 'by term'. It clearly distinguishes this from sibling exact-lookup tools like fomo_get_user_by_handle and fomo_get_user.

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?

There is no explicit statement about when to use this tool versus alternatives, but the word 'fuzzy' implies it is for partial or inexact matches. The agent must infer from sibling names rather than receiving direct routing guidance.

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