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

No annotations are provided, but the description does disclose some behavioral traits: 'Not a thesis. Not a fill. Does not sign.' This tells the agent that the tool does not perform certain actions (like trading or signing), which is valuable. However, it does not explain what it does do (e.g., does it return data? Does it require authentication? Does it have side effects?). The phrase 'Does not sign' is cryptic without context.

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 short but not well-structured. It is a fragmented, noun-phrase-heavy text that reads like a stream of consciousness. It is not front-loaded with the main purpose; instead, it starts with a URL and cryptic terms. Every sentence is cryptic, making it hard to parse quickly.

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 that there is no output schema and no annotations, the description is the only source of information, and it is insufficient. It does not explain what the tool returns, how it works, or what the user should expect. The jargon ('Bursts', 'Fresh', 'Exits') is undefined. For a tool with zero parameters, it might be acceptable to be abstract, but the description is too vague to be actionable.

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 no parameters, and the schema coverage is 100% (trivially). With zero parameters, the baseline is 4. The description does not need to explain parameters, but it also does not explain what inputs the tool expects, since there are none. The description is somewhat self-contained.

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 cryptic and does not state a clear verb-resource pair. It mentions 'fomoradar.app' and 'Real wallets behind fomo.family handles, scored' but does not explain what the tool actually does (e.g., 'Get scoring analysis for wallets'). The mention of 'Bursts', 'Fresh', 'Exits' adds jargon without clarifying the tool's purpose. It does not distinguish from siblings like talon_radar.

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 guidance on when to use this tool versus alternatives. It does not mention use cases, conditions, or alternatives. The description is purely explanatory of internal concepts, not actionable usage.

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