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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a small amount of context by indicating the return is a wallet 'profile' sourced from Peerlytics, but it does not disclose output shape, pagination behavior, or any other operational traits beyond what annotations provide.

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, readable sentence with no filler. The action and target are front-loaded, and there is no unnecessary elaboration, making it optimally concise for the information it conveys.

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 straightforward read-only lookup, the description plus the annotations and fully covered schema provide enough to identify the required address input. However, with no output schema and a large set of sibling explorer tools, the description does not clarify what the profile contains or when to prefer this tool over peer_market_explorer_search or peer_balance, leaving an agent to infer the correct usage.

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 adds slight meaning by clarifying that the address parameter refers to a wallet address, but the limit, offset, and raw params fields are left to generic schema descriptions like 'Result limit' and 'Offset.' The description does not compensate with additional parameter-level nuance.

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 uses a specific verb and resource: 'Look up a wallet address profile on Peerlytics.' It clearly identifies the action and subject, and the name supports that this is an address-focused explorer tool. It does not explicitly differentiate itself from sibling tools like peer_market_explorer_search, so it misses the top score.

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 about when to use this tool versus alternatives such as peer_market_explorer_search, peer_balance, or other explorer tools. The description merely implies an address-based lookup, but it never states prerequisites, exclusions, or the selection context needed to route an agent correctly.

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