airwallex_list_payouts

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

No annotations are present, and the description does not disclose behavioral traits such as read-only nature, side effects, rate limits, or pagination. The generic routing note adds no behavioral insight.

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 includes redundant identification (e.g., 'Airwallex connector operation `list_payouts` (platform tool `airwallex.list_payouts`)') that wastes space. It is not concise; it lacks essential information while repeating obvious 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?

The description is incomplete: it does not mention what the tool returns (despite having an output schema), any filtering capabilities, or the scope of payout data. The agent cannot determine how to use this tool effectively.

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 'JSON string of arguments for the connector operation', which adds no meaning beyond the schema. With 0% schema description coverage, the description fails to explain the expected structure or purpose of the arguments.

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 merely restates the tool name and route ('Airwallex connector operation `list_payouts`') without specifying that it retrieves a list of payouts. It fails to differentiate from sibling tools like `airwallex_list_balances` or `airwallex_list_transactions`.

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 this tool versus alternatives. There is no mention of prerequisites, context, or scenarios where this tool is appropriate or inappropriate.

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