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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower; the description still earns credit by disclosing what the payload contains — an aggregation of profile, created coins, earnings and locks — which is the key behavioral fact given no output schema. It stops short of stating pagination/limits on the coin list or behavior for wallets with no profile.

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 sentence, front-loaded with the resource and then the returned fields, with zero filler. Everything present earns its place.

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?

Read-only aggregate with no output schema, so enumerating returned fields in the description is the right move and largely covers the gap. Missing are result-shape details an agent would want before calling — whether the created-coin list is truncated, units/format of earnings, and what happens for an unknown wallet.

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?

Only one parameter, and the schema documents it fully (base58 Solana address with a regex pattern) at 100% coverage. The description adds nothing about the wallet argument, so the 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-resource pair ("a wallet's higher.fun profile") and enumerates the constituent data: display name, created coins, creator earnings (paid out/pending) and creator locks. That makes it distinguishable from get_wallet_positions and get_creator_coins, though it never names those siblings to sharpen the boundary.

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?

The phrase "in one call" implicitly signals this is the bundled/aggregate lookup versus the narrower siblings, but there is no explicit when-to-use, when-not-to-use, or prerequisite (e.g., whether the wallet must have created coins). Usage must be inferred.

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