paymentSessions.continuePayment

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

With no annotations, the description carries full burden but fails to disclose critical behavioral traits: it doesn't state whether this operation is idempotent, what side effects occur (does it charge the card?), error handling for failed 3DS, or the return value structure.

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 single sentence is front-loaded and free of filler, but given the 0% schema coverage and complex payment domain, this brevity constitutes under-specification rather than efficient design—it should be earning its place by adding necessary parameter and behavioral details.

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 financial operation handling 3DS authentication flows with nested objects and no output schema, the description is inadequate. It omits flow documentation, parameter details, and behavioral expectations necessary for safe agent invocation.

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 has 0% description coverage. The description mentions '3DS' which loosely maps to the threeDs parameter but provides no semantics for the required clientSecret parameter or the expected structure/format of the threeDs object (additionalProperties: {} offers no guidance).

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 states a specific action ('Continue') and resource ('Ryft payment'), and mentions the 3DS context which distinguishes this from sibling tools like create, capture, or void. However, it could more explicitly clarify the workflow position relative to paymentSessions.create.

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?

It implies usage timing ('after a required action such as 3DS'), but lacks explicit guidance on when NOT to use this versus alternatives like create or capture, and omits prerequisites like requiring a clientSecret from an initial session creation.

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