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

Annotations already mark readOnlyHint as false, so the agent knows it's a mutation. The description adds the critical instruction to display the payment link, which is an important behavioral trait. However, the main description's phrase 'Get payment' is vague about side effects (e.g., does it actually charge the user or just generate a link?). The method parameter descriptions clarify that it returns a URL/address, but the main description does not. 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?

The description is concise: two sentences. The first states the purpose, the second delivers a critical, action-oriented instruction. Every sentence earns its place, and the key information is front-loaded.

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 purpose and the required post-call action, but lacks details about the return value format (no output schema) and prerequisites (e.g., job must be quoted). The instruction implies the job is set up, but explicit prerequisites are missing. Given the tool's complexity (4 params, no output schema), the description is adequate but not fully complete.

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 75% (3 of 4 parameters documented in the schema). The description does not add any meaning beyond the schema; it only mentions 'the chosen method' generically. The schema already provides detailed enum descriptions for engine and method. Thus, baseline 3 is appropriate as the description adds no extra parameter insight.

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 verb 'Get payment' for a 'quoted job' via a chosen method, which distinguishes it from sibling tools like pay_commercial_license (which pays for a commercial license) and settle_x402_payment (a post-payment step). The resource and action are specific.

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 provides clear context: 'AFTER SETTING UP THE JOB you MUST give the payment link to the user immediately'—this indicates the sequencing relative to job setup. However, it does not explicitly compare to alternatives (e.g., when to use pay_commercial_license instead) or state when not to use the tool.

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