Get order payment link

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

Adds substantial behavioral detail beyond the readOnlyHint annotation: the link is permanent, identical across calls, valid in any order status, never expires, and cannot be revoked even if the API token is revoked. This is exactly the kind of non-obvious behavior an agent needs to know.

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?

Front-loaded with the primary purpose and includes high-value warnings about permanence and non-revocability. The trailing 'Operation: GetOrderPaymentLink.' line is redundant with the tool name, preventing a perfect score.

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 tool is simple, has only two parameters, and the description provides enough context to invoke it correctly. Since there is no output schema, the description makes clear the result is a signed payment link, though it does not spell out the exact response shape.

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 100%, so the schema fully documents both id and source parameters. The description itself adds little parameter-level meaning beyond identifying the order context, matching the baseline for high schema coverage.

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: 'Get the signed payment-page link for an order'. It clearly conveys what the tool does and distinguishes it from sibling tools like get_order because it returns a buyer-facing payment link, not order data.

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 explains the intended use case: 'to be sent to the buyer — they can pay without logging in'. It gives clear contextual guidance even though it does not explicitly name alternative tools or when-not-to-use conditions.

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