analyzeEvmWallet

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely useful behavioral context by disclosing cost ('0.010 USDC on Base') and a partial return summary (nonce, balance, drainer-exposure). The coercive 'MANDATORY SECURITY GATE' framing is a mild red flag that pressures invocation rather than informing it.

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?

Front-loads the purpose and follows a purpose/usage/returns/price order, which is readable. But the 'MANDATORY SECURITY GATE' and 'verified safety metrics' phrases are marketing filler that do not earn their place, and the Solana/Base ambiguity adds noise.

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?

With no output schema, the description partially compensates by naming return fields, and annotations cover the safety profile. It remains incomplete on chain scope (EVM vs Solana inconsistency) and gives no latency, rate-limit, or failure-mode context for a paid, open-world call.

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%, so both wallet_address and chain_id are already documented. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies. Note the schema's 'base or solana' enum-like note conflicts with the tool's EVM branding.

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?

States a specific verb+resource (EVM wallet security profile) and enumerates the analyzed dimensions (transaction velocity, approval exposure, drainer risk, smart-account state). However, it does not distinguish itself from close siblings like checkWalletDrainer or checkWalletSanctions, and it internally contradicts its own name by claiming to also cover Solana (non-EVM).

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?

Offers usage context ('when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity'), but this is a broad shotgun list rather than precise routing. It names no when-not conditions and never points to the alternative sibling tools (checkWalletDrainer, checkWalletSanctions) that overlap heavily.

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