suverse_wallet_reputation

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

With no annotations provided, the description reveals key behaviors: the $0.03 USDC cost, the x402 payment flow (returns price/instructions without payment_signature), the on-chain-only data basis, and the 'unknown' tier for unindexed wallets. This substantially covers the tool's side effects and edge cases, though no rate limits or error handling are described.

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 uses three sentences and front-loads the purpose before addressing cost and limitations. It is efficient but somewhat dense, packing a lot of detail into a paragraph format. No redundant words, but the structure could be slightly improved with bullet points.

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 no output schema and no annotations, the description explains what the verdict contains (tier, activity class, flags, stats, trades), the payment/cost model, and the edge case for unindexed wallets. This is fairly complete for an agent deciding whether to invoke it, though it doesn't detail response format or errors beyond the 'unknown' tier.

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 schema already documents both parameters at 100% coverage, so the baseline is 3. The description adds value by clarifying the two-call payment workflow involving payment_signature (unpaid call returns price/instructions; paid call returns full response) and the Solana-specific scope for the wallet parameter.

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 opens with a clear question that defines the tool's function: assessing whether a Solana wallet's trading can be trusted or copied. It enumerates the output components (skill tier, activity class, flags, stats, trades) and the Solana-only scope, distinguishing it from the other suverse_* sibling tools.

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's use case (wallet reputation evaluation) but does not explicitly state when to use it over alternatives or mention exclusions. It notes the Solana-only limitation and payment requirement, which helps, but no alternative tools are referenced or compared.

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