solana_wallet_scan

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

No annotations provided, but description fully discloses payment gate behavior: without '_payment' returns 402 accept-list; with it, returns findings and referral CTAs. Pricing and authorization method are clearly stated.

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?

Four sentences, no redundancy. Front-loaded with what the tool does, followed by payment details. Every sentence adds essential information.

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 two simple parameters and no output schema, the description covers core functionality and payment flow adequately. Lacks detail on response format, but not critical for an agent to select and invoke correctly.

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?

Both parameters are described in schema (100% coverage). Description adds value by explaining the payment mechanism and the conditional behavior of the '_payment' parameter, going beyond schema's basic description.

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?

Description clearly states the action ('Scan a Solana wallet') and specific resources (portfolio value, dust accounts, stale stake accounts, low-liquidity warnings). It clearly differentiates from sibling tools such as solana_wallet_security_audit_rules.

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?

Description explains the tool's purpose and the prerequisite of x402 payment for full response. It does not explicitly state when not to use it, but the context is clear given sibling tools are dissimilar.

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