profile_wallet_smart_money

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

With no annotations, the description carries the full burden. It usefully discloses the concrete analytics computed and that a letter grade (A+ to F) is assigned, which goes beyond the name. However, it omits notable behavioral facts implied by the schema: that a paymentProof unlocks unlimited calls (i.e. there is a metered/paywalled tier), and what happens for wallets with thin or no history.

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?

A single dense sentence that front-loads the resource and output list with no filler. It is well-sized for the tool, though it spends words enumerating metrics while leaving the payment behavior unaddressed.

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?

There is no output schema, so enumerating the returned metrics and the grade scale is genuinely necessary and mostly covers the return shape. Gaps remain around the payment/credits model exposed by the paymentProof parameter and around grading criteria or failure modes for unknown wallets.

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%, including an enum for network and format hints for walletAddress ('0x... or Solana base58'), so the schema already does the heavy lifting and a baseline 3 applies. The description adds no parameter-level meaning beyond the schema, notably leaving the paymentProof paywall semantics unexplained.

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 (analyzes) and a specific resource (a wallet's trading track record), then enumerates the exact metrics returned (win rate, realized PnL, 30-day ROI, hold duration) plus the CopyTradeGrade. It is clearly a per-wallet tool as opposed to the token-level and cluster-level siblings, but it never names those siblings or states the distinction explicitly.

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 guidance on when to call this versus get_smart_money_radar, get_token_whale_activity, or detect_insider_clusters, and no prerequisites or exclusions. The agent must infer from the name and the word 'wallet' that this is the per-address profiling entry point.

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