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

No annotations are provided, so the description carries the burden of explaining behavior. 'List' indicates a read-only, non-destructive operation, but it does not disclose other behavioral aspects such as authentication requirements, rate limits, pagination, or response format. Some transparency is present, but gaps remain.

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, efficient sentence that front-loads the action ('List') and includes all key information: categories, source, and platform. It contains no filler or redundant details.

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 is relatively simple (2 optional parameters, no output schema, no annotations), the description provides a basic understanding but lacks explicit mention of how parameters control the output or how it relates to sibling tools. It is minimally complete but not thoroughly contextualized.

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 description mentions 'trending, newest, or graduated' which aligns with the `type` parameter's enum values, adding context for that parameter. However, it does not explain the `limit` parameter or explicitly tie these words to the schema. With 0% schema description coverage, the description only partially compensates for missing parameter semantics.

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 identifies the tool's function: 'List currently trending, newest, or graduated tokens'. It names the resource (tokens tracked by SolRadar) and the platform (Solana/pump.fun), which distinguishes it from sibling tools like check_token and check_wallet_activity.

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 the tool is for getting token lists, but it does not explicitly explain when to use it instead of check_token or check_wallet_activity. There is no exclusion criteria or direct comparison, so usage guidance is only implied rather than explicit.

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