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

No annotations are supplied, so the description carries the full burden. It does disclose the return shape (pid, paymentUrl, qrPayload) despite no output schema, and "shareable" hints the URL is externally accessible. However, it never states that this is a state-mutating operation, what permissions are required, whether it is idempotent, or what happens at expiry.

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 short sentences with the action and the output front-loaded; nothing is wasted. The trailing clause "for humans or agents" is slightly decorative but does convey the shareable/QR intent.

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?

For a 7-parameter mutation tool with a nested metadata object and no annotations, the description covers purpose and outputs but omits prerequisites, amount requirements, and lifecycle behavior (expiry, cancellation via cancel_payment_request). It is adequate but leaves real gaps an agent would want filled.

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 already explains walletMappingId, amountUsd, amountSmallestUnit, expiryDays, metadata, and externalReference. The description only echoes the vault target and says nothing about the amountUsd vs amountSmallestUnit exclusivity or the default 30-day expiry, so it adds little beyond the schema.

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 ("Create a shareable payment request for a vault") and adds the output artifacts, so an agent knows exactly what is produced. It stops short of differentiating this from nearby siblings such as create_checkout_session or create_payment_product, which also mint payable artifacts.

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?

There is no when-to-use guidance, no preconditions (e.g. vault must exist or be owned by the caller), and no mention of alternatives like create_checkout_session or create_payment_product. The phrase "for a vault" implies the walletMappingId target but leaves selection logic to inference.

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