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

With no annotations, the description carries the full behavioral burden; it does disclose 'read-only' and names the upstream data source (GMGN), which is genuine safety/context value. However, it says nothing about return shape, rate limits, freshness/latency of signals, or whether results are paginated — significant gaps for an annotation-free tool.

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?

A single sentence, correctly front-loaded with the read-only nature and the resource, with the optional market-cap scoping placed last. Nothing is wasted.

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?

No annotations, no output schema, and three parameters at zero schema coverage, one of which (signalTypes integer codes) is entirely unexplained. For a tool whose primary input is an opaque numeric enum range, the description does not supply enough for correct invocation.

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 gestures at the market-cap bounds, adding no format or semantics beyond the parameter names. The signalTypes parameter is an array of integers bounded 1–21 with no mapping to meanings anywhere, so an agent cannot construct a valid call — this is the most serious documentation hole.

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 and resource — reading GMGN market signals on Robinhood Chain — and gives concrete examples (smart-money buys, volume spikes). It does not distinguish itself from siblings like agentcity_robinhood_smart_money, so an agent cannot tell from the description alone why it should pick this over that one.

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 when-to-use instruction, no exclusions, and no named alternative despite an obvious overlapping sibling (agentcity_robinhood_smart_money). The agent must infer usage entirely from the examples of signal content.

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