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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the description adds genuine extra context: room calls lag 'a few minutes behind unless a member asks,' and the explicit disclaimer that flags are findings and trader counts are counts, not buy signals. No latency on the other streams or rate limits are mentioned, keeping it short of a 5.

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?

Front-loads the core purpose, then the three streams, then the incremental-polling instruction, then the caveat. Dense but every clause carries information; the nested parentheticals make it slightly heavy to parse.

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 an aggregation call with no output schema, the description covers what comes back, the cross-chain scope, incremental-refresh behavior, and interpretability caveats. The remaining gap is the underspecified parameter formats, which the schema leaves bare.

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 coverage is 0% and both parameters are undocumented in the schema. The description indirectly explains `since` (pass the prior as_of to get only changes) and implies `chain` via 'Robinhood Chain and Solana,' but omits the timestamp format and the accepted chain values, leaving gaps an agent must guess at.

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?

States a specific verb+resource ('what is happening right now') and enumerates the three content streams it aggregates (FOMO app tokens with PumpPill's read, PumpPill room calls, newly flagged Robinhood Chain tokens). It is clearly an aggregation tool, though it does not explicitly contrast itself against siblings like fomo_gathering, room_calls, or rh_flagged_recent that supply the same data individually.

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?

Gives concrete usage guidance: 'Pass the as_of from the last answer as `since` to get only what changed,' which tells the agent how to use it for polling. It also frames the use case ('what is happening right now'), but offers no explicit when-not or alternative-steering guidance against the sibling single-stream tools.

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