Wallet trading profile

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a genuinely useful trait — cost of $0.01 per call and that calls will return 402 without a payment configured — but says nothing about auth requirements, rate limits, or whether the operation is strictly read-only beyond the 'profile' framing.

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?

Three sentences, front-loaded with purpose then usage then cost. The payment/402 parenthetical is slightly verbose but earns its place as actionable behavioral info.

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?

For a simple single-parameter read tool with no output schema, the description substitutes well by listing the profile fields returned and disclosing the payment/402 behavior. Remaining gaps around auth and rate limits are minor given the tool's low complexity.

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%: the single 'address' parameter is fully documented as a base58 Solana wallet address. The description adds no format, constraint, or example beyond the schema, so baseline 3 applies.

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 and resource — 'Lifetime trading profile of one Solana wallet' — and enumerates the returned fields (PnL, ROI, win rate, hold times, flags, recent tokens). The resource is clearly wallet-focused, which separates it from the token- and trade-oriented siblings, though no sibling is named 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?

Gives a concrete when-to-use condition: 'Use it to judge a buyer or seller you saw in a trade list.' No when-not or alternative tools are named, so it falls short of the explicit routing seen in the best definitions.

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