noticer_pay_with_existing_link

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

Goes well past the annotations: it discloses that a real payment can be submitted, that approval alone is not settlement and settlement is not verified evidence, that credentials stay in private subprocess memory, that only sanitized status and an approval URL are returned, and that no downstream action runs. That is exactly the behavioral context annotations cannot express.

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?

Purpose is front-loaded in the first sentence and each subsequent line adds a distinct constraint (requirements, prohibitions, credential handling). Dense but not padded; slightly long, though most of the length is load-bearing safety guidance.

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?

An output schema exists, and the description still characterizes the return (sanitized status plus approval URL) and rules out settlement inference. For a single-shot payment tool, nothing an agent needs to invoke it safely is missing.

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 0%, so the description must carry parameter meaning. It does indirectly: 'exact USD 1' pins amount and currency, 'SAME check_label/request' names check_label's role, and 'both local consent and the wallet's approval' implies what confirmed gates — but it never explicitly maps these to the four parameter names or describes formats/types for amount, currency, or confirmed.

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 ('pay for one eligible saved receipt') plus the exact payment rail ('existing authorized Link wallet'), which cleanly separates it from siblings like noticer_payment_challenge and noticer_run_receipt. An agent can tell what this does without opening the schema.

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?

Explicit preconditions (separate exact USD 1 consent, both local consent and wallet approval required), explicit sequencing (resume only the SAME check_label/request, present any approval_url), explicit next step (noticer_get_verified_receipt after settlement), and explicit exclusions (never install software, log in, switch payment methods, or create a replacement request after denial, expiry, or an uncertain payment).

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