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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful operational details: the $0.01 per call cost, the payment proof handshake, and SUSPICIOUS criteria such as homoglyph impersonation and no liquidity. However, 'quarantine flagged tokens' is ambiguous and could be read as a state-changing action despite the read-only annotation, so the description could be clearer about whether quarantine is a classification or a returned calldata result.

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 compact at two sentences and front-loads the cost and primary purpose. The feature list is dense but readable. The closing 'Protect your wallet from scam airdrops' is somewhat redundant with the opening 'Airdrop & dust-token defense,' so it is not maximally efficient.

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 3-parameter tool with strong annotations, the description covers the core use case, cost, and payment flow. However, there is no output schema, and the description does not describe the return shape or clarify the 'quarantine' behavior. An agent could likely invoke it correctly, but it might not know exactly what response to expect or how to interpret the result.

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 schema documents the optional payment proof and retry flow, which supports the baseline of 3. The prose description adds little parameter-level meaning beyond 'classify any token,' and the schema's 'Path parameter' descriptions are thin, but the high coverage keeps this dimension at an acceptable level.

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 actions: classify tokens as KNOWN/SUSPICIOUS, quarantine flagged tokens, and get safe burn calldata, all framed as 'Airdrop & dust-token defense.' This is specific and understandable. However, it does not explicitly differentiate itself from sibling tools like token_security or wallet_analysis, so it stops short of a perfect score.

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 gives a clear context: 'Protect your wallet from scam airdrops' and lists the relevant features. It implies when an agent would use it, but it does not name alternatives or state when not to use it. Sibling tools like token_security and wallet_analysis occupy adjacent territory, so explicit routing guidance is missing.

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