solana_trending

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

Annotations are absent, so the description carries the full burden. It discloses pay-per-call cost and the notion of being a live feed, but does not state whether the operation is read-only, what error handling or rate limits exist, or how the response is structured. For a tool that agents will call, these are significant omissions.

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 concise, with three short sentences that front-load the core purpose first. The second sentence about being a fresh feed adds a slight redundancy but still conveys usage context. The cost mention is important and well placed. There is minimal fluff, and it is easily skimmable.

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 tool has no output schema, the description should at least indicate the nature of the returned data (e.g., an array of pair objects with volume fields), but it only says 'DEX pairs' without structural details. It also omits any authentication or setup prerequisites. For a simple tool with no parameters, this is still incomplete for an agent that needs to consume the response correctly.

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 tool has zero parameters, so schema coverage is 100% by default. The description does not need to explain parameters. The baseline for 0 parameters is 4, and no additional parameter information is required.

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 clearly states the tool returns live trending/new Solana DEX pairs ranked by 24h volume. The resource and sorting criterion are specific, and the purpose is distinct from sibling tools like solana_token or solana_account. Even though the verb is implicit, the meaning is unambiguous.

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 implies this tool is for retrieving current market data (trending/new pairs) and mentions it is a 'fresh feed for agents', suggesting repeated polling. However, it gives no explicit guidance on when to use this tool versus the siblings (e.g., solana_health for network status, solana_token for token details) nor any exclusions. Usage context is implied but not explicit.

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