Claim Stealth Payment

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

The description discloses key derivation, environment key usage, and that private keys never pass through AI. This adds value beyond the destructiveHint annotation. No contradiction with annotations.

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?

Two sentences: first states action, second explains security and key inputs. No redundancy; all information is essential and well-structured.

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 description covers the core action and security but does not mention prerequisites (e.g., prior scan-announcements) or output details. Output schema exists, so return values are likely documented elsewhere.

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 coverage is 100%, but the description adds context that only ephemeralPublicKey and to are needed (others optional/default). This helps the agent prioritize inputs beyond schema descriptions.

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 clearly states the tool derives the stealth private key and withdraws funds in one step, specifying required inputs (ephemeral public key from scan-announcements, destination address). It distinguishes from siblings like generate-stealth-address and send-stealth-payment by focusing on claiming.

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?

The description implies usage after scanning announcements but lacks explicit when/why advice or exclusion criteria. It does not compare to sibling tools or state prerequisites clearly.

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