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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description nonetheless adds real behavioral context beyond them: a fixed 30-day lookback window, a restriction to 'tracked' wallets only, and the fact that results are ranked by overlap. It omits any note on pagination or truncation behavior, but that is also covered in the schema's limit field.

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 opening two sentences are tightly front-loaded and earn their place. However, roughly half the text is a redundant parameter glossary that duplicates a fully documented input schema, which dilutes an otherwise efficient description.

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 an output schema present, return values need not be explained, and the description covers what is returned, the time window, and the ranking basis. What is missing is routing guidance against the many sibling wallet/token comparison tools, which an agent would need to pick this tool confidently.

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%, so the baseline is 3. The description's parameter lines are essentially a re-listing of what the schema already documents (blockchain enum values, address, limit default) and add no new semantics such as address format or the trimming caveat, which live only in the schema.

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 precise resource and scope: 'Other tracked wallets that traded the same tokens as this one over the last 30 days, ranked by overlap.' That is far more specific than a restatement of the name and tells the agent exactly what population is returned. It does not, however, name or differentiate itself from adjacent siblings such as compare_wallets or get_wallet_tracker, so it falls short of a 5.

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?

'Useful for finding groups that move together, which can indicate coordination' gives an implied use case, which is better than nothing. There is no explicit when-to-use vs when-not, no named alternative (e.g. compare_wallets for wallet-to-wallet comparison), and no prerequisites such as requiring the wallet to be tracked first.

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