gate_prepaid_balance

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

No annotations provided, so description carries burden. Explains prepaid mechanism (deposited once, debited per request, no signing each time). Declares read-only nature clearly. Could mention auth requirements or rate limits, but sufficient.

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?

One sentence with parenthetical qualifier and 'Read-only'. Front-loaded key info, no filler. Efficient given tool simplicity.

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?

For a simple tool with one parameter and no output schema, description covers purpose, behavior, and parameter semantics. Does not specify output format, but not critical given low complexity. Differentiates from siblings adequately.

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 has 100% coverage, but description adds context: 'Balances are tracked per token, so USDC and USDT are separate pots' and notes default. This adds meaning beyond enum description.

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?

Clearly states it shows the prepaid balance for a stablecoin, with specific verb 'show' and resource 'pre-paid balance'. Distinguishes from siblings like gate_prepaid_deposit (deposit) and gate_get_price (price).

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?

Indicates read-only nature but lacks explicit when-not-to-use or alternatives. Implies usage for checking balance without signing, but no direct guidance on when to use this versus gate_fetch or other tools.

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