paymentSessions.create

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the mutation type ('Create'). It omits critical details like whether this initiates an immediate charge, requires subsequent capture calls, supports idempotency, or what errors may occur.

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 efficient and front-loaded with no waste, but it is inappropriately sized for the tool's complexity (8 parameters, 3 enums, nested objects). It suffers from under-specification rather than verbosity.

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?

Completely inadequate for a complex financial mutation tool with no output schema and zero parameter documentation. The description fails to explain the payment session lifecycle, return values, or integration requirements (e.g., whether follow-up calls to capture/continuePayment are needed).

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 0% and the description fails to compensate by explaining any of the 8 parameters (amount, currency, entryMode enums, captureFlow semantics, metadata structure). It mentions neither required fields nor the purpose of critical business logic parameters.

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 'Create a Ryft payment session' is essentially a tautology that restates the tool name (paymentSessions.create) with minor spacing and the addition of 'Ryft' (the product name). It fails to distinguish what a payment session represents versus sibling operations like update, capture, or void.

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?

No guidance is provided on when to use create versus the numerous sibling session operations (capture, continuePayment, refund, void, update) or prerequisites like customer existence. The description lacks any conditional logic or alternative suggestions.

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