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

With no annotations provided, the description carries the full disclosure burden. It does add one genuinely useful behavior — webhook URLs are redacted to origin, which affects what an agent can do with the results. However, it leaves read-only safety, pagination, and empty-wallet behavior unstated.

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?

A single, tight sentence with the verb and resource front-loaded and the redaction caveat cleanly parenthesized. Every word earns its place, and nothing is duplicated from the schema.

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?

Since no output schema exists, the description should at least hint at return shape; the redaction note partially does this by describing what is NOT returned. But subscription fields, pagination, and empty-result behavior are all unspecified. This is adequate for a single-parameter read tool but has clear gaps.

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%, so the description must compensate. It does clarify that the wallet parameter is the subject whose subscriptions are listed, adding semantic meaning to the bare schema field. But it adds nothing beyond that role, such as address format expectations or edge-case behavior.

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 ('List') with a specific resource ('a wallet's notification subscriptions'), and the parenthetical about webhook URL redaction sharpens the scope further. The read-oriented verb clearly distinguishes it from the sibling mutation tools subscribe_notifications and unsubscribe_notifications.

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?

No guidance is given on when to call this vs. alternatives, and there are no exclusions, prerequisites, or contextual cues. The read/write separation from the subscribe/unsubscribe siblings is only implied by naming conventions, never stated.

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