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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond the schema: this is a paid call costing 0.010 USDC and payable on Base or Solana, which affects whether an agent should invoke it. It does not mention rate limits or latency, but the payment disclosure is the key operational fact.

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?

Two sentences, both front-loaded with the highest-value information: what is analyzed first, cost second. No filler, no repetition of the tool name.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, for a paid, multi-signal analysis tool, the description leaves gaps: it never states the chain_id semantics, nor when this should be chosen over cheaper single-purpose siblings, which is precisely the decision an agent faces here.

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 coverage is only 50%: wallet_address is documented in the schema, but chain_id has no description at all, only a default of 8453. The description says 'on Base', which does nothing to explain whether chain_id is configurable or what other chains are valid, and the mention of Solana for payment only deepens the ambiguity about chain scope. It does not compensate for the coverage gap.

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 names a specific resource (EVM wallet security profile) and enumerates the exact analyses performed: transaction velocity, approval exposure, drainer interaction risk, and smart-account state. The word 'Comprehensive' signals breadth versus the focused siblings like checkWalletDrainer, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The word 'Comprehensive' and the price line imply this is a heavier, paid option best used when a full risk picture is needed rather than a single check, but the agent must infer that.

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