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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds value by naming return fields and noting optional pagination inputs, but it doesn't disclose auth requirements, rate limits, or pagination semantics beyond 'cursor'.

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 English portion is reasonably front-loaded and compact, but the description then repeats itself verbatim in Chinese, which adds no new information for a typical agent. Half the text is redundant duplication.

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?

There is no output schema, so naming balance_cents, transactions and next_cursor is genuinely useful. However, with zero schema parameter documentation, the description leaves pagination and limit behavior underspecified, and offers no sibling routing for a tool set containing several credit-related tools.

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 description coverage is 0%, so the description must compensate, but it only repeats parameter names ('optional limit and cursor'). It does not explain what limit controls, the maximum of 100, how to obtain or reuse a cursor, or the default page size.

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 and resource: 'Get credit balance' and 'Read member credit balance and recent transactions'. Clear what it does, but it does not distinguish itself from balance-adjacent siblings such as get_buy_credits_link or pay_style_topup.

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?

The description gives no when-to-use guidance, no exclusions, and no alternatives. An agent cannot infer from the text alone whether this is the right tool versus get_buy_credits_link or pay_style_topup; only the tool name hints at usage.

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