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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds genuinely new behavior: ordering ('newest first') and that each record carries its message and signature. It stops short of pagination or volume behaviour, which matters for this tool.

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?

It is a single front-loaded clause naming the resource and ordering, which is efficient. But the sentence is cut off ('so anyone re-checks each...') and trailing rationale adds no callable information.

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?

The content of the returned records is described well enough to substitute for a missing output schema. However, with one undocumented parameter and no mention of result volume or pagination, the definition leaves a gap for an enumerating tool.

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% and the single parameter (limit) is undocumented in both schema and description. The phrase 'Every identity-wallet link' arguably conflicts with an implicit limit default, and no guidance on the value or default is given.

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 (identity-wallet links) and its payload (message and signature), which is more specific than a bare name. However, it never uses an explicit verb like 'list' or 'return', and it does not distinguish itself from near neighbours such as wallet_get, wallet_link, or wallet_link_message.

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 statement of when to call this versus alternatives like wallet_get or wallet_link_message, nor any prerequisite or exclusion. The only usage signal is the implicit 'all links' scope, which the agent must infer.

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