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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description contributes the identity-string formats (acct:<id>, agent:a-<12 hex>), which is genuine extra context, but it is truncated and says nothing about what happens with unlinked identities or empty results.

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 text is short, but that brevity comes from being cut off ('...or the identity behind a...') rather than from tight editing. The sentence is not self-contained, so the agent cannot act on it with confidence.

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 four-parameter, zero-coverage, no-output-schema lookup, the description should explain the reverse direction (identity from wallet), the role of `proof` and `address`, and what is returned when there is no link. None of that is present because the description ends prematurely.

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 0% for four parameters, so the description must carry the load and it does not. It hints at the format of `identity` but leaves `key`, `proof` and `address` — including what proof is for — entirely unexplained, and truncation removes the rest of the sentence.

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 identifies the resource (a Solana wallet / the identity behind it) and indicates a two-way lookup, but the operating verb is only implied by the name and the sentence cuts off mid-clause, so the purpose is recognizable yet not fully stated. It does not differentiate itself from wallet_link or wallets_linked, which are close siblings.

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 when-to-use guidance, no statement of prerequisites, and no routing to alternatives such as wallets_linked (list all linked wallets) or profile_get. The agent must infer the use case from the name alone.

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