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

The description labels the tool as 'Read-only', which appropriately signals non-destructive behavior. Since no annotations are provided, the description carries the full burden for transparency. However, it does not disclose other important traits such as authentication requirements, rate limits, or data freshness. The read-only mention is helpful but insufficient for full behavioral clarity.

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 a single, front-loaded sentence that immediately conveys the tool's function. It is concise and avoids unnecessary words. However, it could be slightly expanded to include parameter hints without losing conciseness.

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 the lack of an output schema, the description should hint at the return format (e.g., a list of token objects with properties like name, symbol, price). It also does not mention behavior like empty results or error handling. For a simple tool with two parameters, the description is incomplete for an agent to fully understand what to expect from the response.

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 input schema has two parameters (limit and interval) with zero description coverage. The tool description does not explain the meaning or usage of these parameters. While the defaults and enum hints provide some inference, an agent would benefit from explicit guidance on how 'limit' controls the number of tokens returned and what each 'interval' value means for the trending calculation.

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 states 'Robinhood Chain trending tokens from GMGN' and declares it as read-only. This clearly identifies the resource and action (retrieving trending tokens), distinguishing it from siblings like 'hoodly_list_robinhood_launches' which lists launches. However, it lacks an explicit verb like 'list' or 'get', which would make the purpose more precise.

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 its siblings. There are six sibling tools with different functionalities (compare, research, daily brief, kline, launches, launchpads), but no criteria are given for selecting 'trending tokens' over them. This omission leaves the agent to guess the appropriate context.

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