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

Annotations cover the safety profile (readOnly/openWorld), and the description adds meaningful context beyond them: the GoPlus Security data source, the exact verdict taxonomy (clean/caution/high-risk/flagged/incomplete), and the paid x402 pricing ($0.03). It does not disclose latency, rate limits, or failure behavior on partial chain coverage, keeping it short of a 5.

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-loaded with the core purpose and packed with useful detail (data source, verdicts, pricing) in minimal space. The opening clause runs long, but nearly every element earns its place and nothing is filler.

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 carries the return-shape burden well by enumerating the main output sections and the verdict values. It leaves minor gaps around the 'incomplete' verdict's cause and Solana limitations, but is otherwise sufficient for an agent to call the tool 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?

Schema coverage is 100%, so both parameters are already documented. The description reinforces the chain behavior by listing supported networks and noting 'Solana: holdings only', which adds a semantic nuance, but it does not go beyond what the schema's chain description already conveys — the baseline 3 for full coverage is appropriate.

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 resource and scope — a combined wallet risk and activity report — and enumerates exactly what it returns (reputation, approvals, scam tokens, portfolio with USD values). This lets an agent distinguish it from siblings like wallet_portfolio, token_audit, and token_report without opening any schema.

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?

Gives clear situational context: 'vet a counterparty before you transact'. This tells the agent when the tool applies. However, it never names an alternative or a when-not-to-use condition (e.g. use wallet_portfolio for holdings only, token_audit for a single token), so routing is left partly to inference.

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