jupiter_getTokenList

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

No annotations are provided, so the description carries the full burden. The description explains the return data but does not explicitly state that the operation is read-only or disclose any rate limits or other behavioral traits. While "Get" implies a read operation, explicit transparency would improve it.

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 two sentences with no wasted words. It front-loads the action and filter criterion, then lists the return data. It is efficient and easy 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?

Given the simple parameter structure and lack of output schema, the description provides sufficient context about what the tool does and returns. It does not cover pagination or response format, but for a token list query, the current level feels adequate.

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 one parameter with 100% coverage. The tool description adds context by listing the return fields (metadata, organic score, price, audit info), which goes beyond the schema's parameter description. This adds meaning for the agent in understanding what data will be retrieved.

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's purpose: to retrieve Jupiter tokens filtered by tag ("verified" or "lst"). It specifies the returned data (metadata, organic score, price, audit info), which distinguishes it from related tools like jupiter_searchTokens or jupiter_getPrice.

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 alternatives such as jupiter_searchTokens or jupiter_getTokenInfo. There is no mention of when not to use it or which scenarios it is best suited for.

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