get_token_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention that the list is sorted and filtered by parameters with defaults, or that there is no pagination limit. The term 'top tokens' is vague and doesn't explain sorting behavior or any potential API constraints.

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 concise sentence with no wasted words, which is structurally acceptable. However, it is under-specified, lacking essential information about sorting and parameters, so it doesn't earn full marks for being appropriately sized.

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 absence of an output schema and annotations, the description is incomplete. It doesn't describe the expected output structure, the meaning of 'top', or any pagination or data freshness details. For a tool with several similar siblings, more context is needed to set expectations.

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 coverage is 0% and the description adds no meaning to the parameters. It doesn't explain what 'limit', 'sortBy', or 'direction' control, nor does it clarify the meaning of 'top'. The description gives no hints about the parameter values, making it of no help beyond the schema.

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 gets a list of top tokens from Solscan, using a specific verb and resource. It is distinguishable from siblings like get_token_meta or get_token_price, though it doesn't explicitly differentiate from get_token_trending, which could overlap.

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 like get_token_trending or get_token_holders. There is no mention of prerequisites, typical use cases, or contexts where this tool is preferred.

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