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

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds real value on top with the short-lived link lifetime, the 'never request a token or private key' security guardrail, and 'Do not automatically retry,' which explains the non-idempotency. It does not disclose what the link creation affects or why the destructive flag is set.

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?

Four short, front-loaded sentences; the core action comes first and each later sentence adds a distinct instruction (display, wait, security, retry policy). Slightly clipped phrasing ('before preparing') costs a point.

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 one-parameter tool with no output schema, the description covers the action, the precondition, the follow-up sequence, and key safety behavior. It leaves out link expiry duration and what happens if the link is not redeemed, which keeps it below a 5.

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 carry intentId, and it only does so implicitly by mentioning an 'existing 55 USDC Intent.' It adds the meaning that the intent must be pre-existing but gives no format, ID origin, or lookup guidance for the single parameter.

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?

States a specific verb and resource ('Create a short-lived owner login link') plus its scope ('for an existing 55 USDC Intent'), which separates it from prepare_wallet_signature and submit_wallet_payment. It stops short of naming a sibling, so differentiation relies on inference.

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?

Implies the precondition (an intent must already exist) and gives clear operational steps: show the URL to the owner, wait for their Phantom connection before preparing. It does not state explicit exclusions or name the alternative tool to use when no intent exists.

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