fomo_trading_activity

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

No annotations are provided, so the description must carry the behavioral burden. It only says 'feed,' giving a weak sense of a stream/list, but it does not disclose ordering, pagination, time window, or whether it is read-only. There is no contradiction with annotations, but there is also almost no behavioral disclosure.

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 definition is very short, which is fine, but it is under-specified rather than appropriately concise. It consists of a single noun phrase and does not structure information about behavior, parameters, or usage that an agent needs.

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?

With 2 undocumented parameters, no output schema, no annotations, and many sibling feed tools, this description is insufficient for correct invocation. An agent cannot tell what the response looks like, what threshold filters, or how this differs from other feed endpoints.

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 does not compensate. 'limit' may be inferable as a count, but 'threshold' is entirely ambiguous—threshold for what? No units, defaults, or filtering semantics are provided.

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 identifies a global trading activity feed, which adds a scope qualifier, but it lacks a verb and does not state what the feed contains (trades, swaps, transactions). It is not a tautology because 'global' adds some distinction, but it remains vague about the exact resource being returned.

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 siblings like fomo_get_trades, fomo_token_feed, or fomo_get_clan_feed. The word 'global' implies a broad use case, but the description never states conditions, exclusions, or alternatives.

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