Pay Wallet

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

No annotations are provided, so the description carries the full burden. It states 'pay' which implies a destructive mutation, but does not disclose behavioral traits like idempotency, authentication requirements, or confirmation steps. The required confirmSubmitPayment parameter hints at a confirmation mechanism but is not explained in the description.

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 a single sentence with no redundant words. It is front-loaded with the action and resource, making it easy to parse quickly.

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?

Despite having only 2 parameters and no output schema, the description is too brief. It fails to provide context about what 'pending checkout' is, how to obtain it, or what the pollCount parameter controls. A payment tool requires more behavioral detail to ensure safe 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 description coverage is 50%: only confirmSubmitPayment has a description in the schema. The tool description does not explain either parameter (pollCount or confirmSubmitPayment). pollCount, a numeric parameter with constraints, is left undocumented, which is a significant omission.

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 action ('pay') and the resource ('saved pending checkout using wallet balance'). It distinguishes from sibling tools like ninja_pay_saved_card which pays with a saved card, making the purpose 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?

No guidance on when to use this tool versus alternatives such as ninja_pay_saved_card or ninja_initiate_stc_pay. The description implies it's for a specific scenario but doesn't provide explicit usage context.

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