airwallex_list_balances

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

With no annotations, the description must disclose behavioral traits. It mentions routing and scope but does not explicitly confirm the operation is read-only, describe side effects, or indicate required permissions beyond the implied JWT scope.

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 short (three sentences) but includes irrelevant routing details (e.g., '/api/tools/invoke') that do not aid an AI agent in correct invocation. The first sentence is clear, but the second sentence adds little value.

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?

Although the tool has an output schema, the description does not mention return values or behavior. For a list operation with a flexible JSON argument, more context on expected output or filtering is needed for completeness.

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 schema has 0% description coverage, and the description merely restates the schema by noting that 'arguments' is a JSON string. No explanation of what keys or values are expected is provided, limiting its usefulness.

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 identifies the tool as an Airwallex connector operation to list balances, with a clear verb-resource combination. However, it does not specify the exact type of balances (e.g., account or wallet) or provide differentiation from sibling tools like airwallex_list_payouts.

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 such as airwallex_list_payouts or airwallex_list_transactions. There is no mention of prerequisites or exclusions.

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