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

Annotations already cover read-only/idempotent safety, so the description correctly spends its words elsewhere: the auth requirement, the fact that the field list is unverified, and that extra_params are 'forwarded verbatim.' The uncertainty disclosure ('Pipeworx has not been able to verify the full field list') is unusually valuable context that annotations cannot carry. Return shape and pagination behavior are left unstated.

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?

It front-loads what the tool does before the caveats, and every sentence carries information (scope, unverified fields, Pro-tier key requirement). It is dense with em-dashes and nested clauses, which makes it slightly harder to parse than it needs to be, but nothing is wasted or repeated.

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?

For a zero-required-parameter, open-world screener with an escape-hatch object parameter, the description supplies the three things an agent actually needs: auth gating, field-set uncertainty, and where to put unlisted filters. With no output schema, the missing piece is any hint of what the response looks like or how paging terminates.

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 100%, so the baseline is 3 and the description must earn above it. It does, by explaining the non-obvious contract: undocumented filters/windows should be routed through extra_params from Solscan's own docs, and the v2 sort_by vocabulary is broader than the v1 examples in the schema. That adds meaning beyond the per-parameter descriptions.

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 opening clause names a specific verb and resource: 'Token List V2 screener — sorts/filters tokens over 170+ metric fields across nine time windows.' That is enough to tell it apart from siblings like get_token_holdings or get_token_meta, which return holdings/metadata rather than sorted screens. The rest of the sentence is caveats, so the core purpose is stated once and then not reinforced.

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?

It gives a clear when-not condition: 'Pro tier — requires your own Solscan API key (Pipeworx's platform key is Free tier and cannot call this).' That is a genuine gating rule an agent needs before invoking. It stops short of naming a sibling to use instead when the user lacks a Pro key, so it does not reach a 5.

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