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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context beyond annotations: public handles/wallets only, and access-tier-dependent output ('headline numbers only' without a trial/paid key). It does not describe return structure or error behavior, but the added tier limitation is meaningful.

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 definition is compact and front-loads the caller context before listing metrics. The metric list is dense but each item is informative, and the scope/access constraints are placed at the end without redundant repetition.

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 one-parameter read-only scorecard tool with no output schema, the description gives a strong content-level summary of what the scorecard includes and notes the key access limitation. It could be more explicit about response shape or invalid/private-handle behavior, but it is largely sufficient for selection and invocation.

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 description coverage is 100%, and the single parameter is already documented as a wallet address, pump.fun username, or X handle. The description reinforces the 'public' constraint but adds no new syntax or format details beyond the schema, so the baseline of 3 is appropriate.

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 is highly specific about the resource and the computed metrics: it names a public pump.fun caller and enumerates buy-before-call frequency, median lead time, sell-within-1h frequency, 50%+ drawdown frequency, serial-launcher calls, and creator-to-caller transfers. That is enough to distinguish it from token-level tools like token_manipulation_score, though it does not explicitly name competing siblings.

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 scope constraints — 'Public handles and wallets only' and 'Without a trial/paid key: headline numbers only' — which help decide eligibility. However, it does not state when to use this instead of trace_wallet, token_manipulation_score, or other sibling tools, so guidance is 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.