fomo_token_allow_list

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

With no annotations and no output schema, the description carries the full burden of behavioral disclosure. It only states that the tool provides a 'detailed token allowlist,' but does not reveal whether it is a read-only operation, what format the allowlist takes, whether it requires authentication, pagination, or any side effects. This is heavily insufficient for an agent to predict tool 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 extremely brief (two words), but this brevity is under-specification rather than effective conciseness. It adds little information beyond the tool name and does not earn its place because it merely restates the purpose in vague terms. A useful description would require at least a full sentence explaining the tool's function.

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?

The tool is extremely simple (no parameters, no output schema), but the description still fails to convey what the allowlist contains, how it relates to other token tools, or what an agent should expect as a response. Given the many sibling tools with similar token-list purposes, this description leaves the tool's role ambiguous and incomplete.

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 tool has zero parameters and the schema is empty, so schema description coverage is trivially 100%. The description does not need to explain parameter semantics because there are none. The baseline for zero parameter tools is 4, and no further clarification is required.

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 'Detailed token allowlist' is essentially a restatement of the tool name with the adjective 'detailed' added. It lacks a verb or action, so it does not convey what the tool actually does (e.g., retrieves, lists, validates). It also does not differentiate this tool from siblings like fomo_supported_transfer_tokens or fomo_verified_tokens, which likely also return lists of allowed or verified tokens.

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?

The description provides no guidance on when to use this tool versus alternative token-related tools. There is no mention of use cases, conditions, or exclusions. An agent would have to guess based on the name alone, making selection unreliable.

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