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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile, so the bar for additional disclosure is lower. The description adds real behavioral context beyond the annotations: the call costs $0.01 (a paid operation, which an agent should know before invoking), and the data is 'sampled' (age) with a 'failed-transaction rate' and behavioural flags, implying heuristic rather than exhaustive computation. No contradiction with annotations exists.

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?

The description is a single, efficient sentence with the core subject ('On-chain profile for a Solana wallet') front-loaded, followed by a compact enumeration of report contents and a closing cost note. Every clause earns its place, and the cost disclosure is important enough to include. No filler or redundancy.

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 full annotation coverage and 100% schema coverage, this is largely complete. Because there is no output schema, the description compensates by enumerating what the report contains (SOL balance, token positions, recent activity, etc.), giving the agent a sense of the return payload. The main gaps are the unspecified nature of 'behavioural flags' and the output format, but these are minor relative to the annotated safety profile and fully documented parameter.

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%: the single required parameter `address` is already described as a 'Solana wallet address (base58)' in the schema. The description only reinforces that the wallet is Solana-based and does not add syntax, format, or validation detail beyond the schema. With full schema coverage, the baseline of 3 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?

The description states a clear resource (Solana wallet) and a specific deliverable (an on-chain profile report) and enumerates its contents concretely: SOL balance, token positions, recent activity, sampled age, failed-transaction rate, and behavioural flags. It differentiates clearly from the token-focused siblings (check_token_holders, check_token_price, etc.) since it targets a wallet address rather than a token. An agent can immediately tell this apart from the sibling set.

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 named alternatives or exclusions. The usage context is only implied by the content (a wallet-level profile), which an agent can infer but is not told. It does not state, for example, 'for a token-level report, use check_token_* instead.' This is adequate but leaves the selection logic unstated.

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