airwallex_create_payment

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

No annotations are provided, so the description must disclose behavioral traits. It mentions routing through `/api/tools/invoke` under JWT/tenant/company scope, indicating authentication needs, but does not describe side effects, idempotency, rate limits, or what happens on success/failure for this creation operation.

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 concise with three short sentences. It front-loads the identity of the tool and includes routing context. However, it could be more informative without becoming verbose.

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?

Given the tool has no annotations and a single parameter with no schema descriptions, the description is incomplete. It does not explain what the `create_payment` operation does, what the JSON arguments should contain, or what the output schema returns. An output schema exists but is not referenced.

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?

The only parameter `arguments` is described as a 'JSON string of arguments for the connector operation'. This adds minimal meaning beyond the schema's title 'Arguments'. With 0% schema description coverage, the description should provide more detail about the expected keys and values in the JSON.

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 tool name 'create_payment' clearly indicates it creates a payment via Airwallex. The description references 'Airwallex connector operation `create_payment`' which reinforces the purpose but does not distinguish it from sibling list operations like `airwallex_list_balances`.

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. The description only states it's a connector operation and the routing, with no context on prerequisites, suitable scenarios, or when to use other Airwallex tools.

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