getAccountWithdrawalInfo

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

Annotations already declare readOnlyHint=true and openWorldHint=true, establishing a safe query operation. The description adds minor behavioral context by explaining that the tool returns the available withdrawal amount for each queried coin, and it constrains coinName to comma-separated values with a max of 20 coins. It does not go deeper into rate limits or error conditions, but the annotation coverage keeps this acceptable.

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?

Two sentences with no filler. The purpose is front-loaded, and the parameter constraint is presented as a crisp bullet. Every sentence earns its place.

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 single-parameter read-only tool with no output schema, the description is complete: it states what the tool returns, which account type applies, and the exact input requirement. Nothing critical is missing for an agent to invoke it correctly.

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 coverage is 0%, so the description must compensate for the bare string parameter. It meaningfully does so by stating that coinName is required, accepts one or more comma-separated coin names, and caps the list at 20 coins. This goes well beyond the schema, though it could still benefit from examples of valid coin names.

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?

States a specific verb ('Query'), resource ('available withdrawal balance'), and scope ('specified coin(s) in the Unified account'). The description clearly communicates what the tool does, though it does not explicitly differentiate it from nearby siblings like getWithdrawableAmountByCoin or getWalletBalance.

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?

Provides clear context: use this tool when you need the available withdrawal balance for specified coins in a Unified account. It does not explicitly mention when not to use it or name alternative tools, but the scope is specific enough to guide selection.

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