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

With readOnlyHint/idempotentHint already declaring the safety profile, the description still adds the crucial behavioral fact that this tool does not move money itself: it returns a payable endpoint, the agent's own wallet pays, and Loadbay never holds funds. That two-step flow is exactly the context an agent needs and is not derivable from annotations or schema.

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?

Three sentences, no waste, and the gating condition is front-loaded before the mechanics. Each sentence carries distinct information: when to use, what it does, and how the payment actually executes.

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?

No output schema exists, so the description compensates by explaining the return value (payable endpoint plus payment details). Combined with full parameter coverage and the custody disclaimer, an agent has everything needed to call it and interpret the result.

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%, so both parameters are already documented (including the USD default of 1 and USDC settlement). The description adds only the 'USDC over x402' framing, which largely restates the schema, so the baseline 3 applies.

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 (tip) and resource (harness author), and the 'x402'/USDC payment rail further pins down the operation. The phrase 'harness author' implicitly separates it from support_loadbay, which targets Loadbay itself, so an agent can route correctly.

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?

'Only when the user asks to tip or pay a harness author' is an explicit use condition that prevents unprompted invocation. It does not name support_loadbay as the sibling alternative for other payment intents, leaving that routing to inference.

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