Trending tokens

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

With no annotations, description must disclose behavior. It only mentions aggregation sources (RugCheck, DexScreener, volume) but omits cost implications, rate limits, or return format. The cost hint '~$0.002 in CIRC' is vague.

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?

Very short (15 words) with no filler. Front-loads cost info, which may not be priority, but overall efficient.

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 low complexity (1 optional param, no annotations, no output schema), description fails to complete context: no return type, no parameter guidance, no behavioral caveats.

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 only parameter 'limit' has 0% schema coverage and is not explained in the description. Its purpose (likely max count) is left to agent inference.

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 verb 'aggregated' and resource 'trending Solana tokens' clearly state the function. It distinguishes from sibling tools like token_price or token_holders, which focus on individual tokens.

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?

Implies use for discovering trending tokens but lacks explicit guidance on when to use this versus alternatives like scan or swarm_feed. No exclusion criteria or prerequisites stated.

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