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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them by disclosing that the call itself is free, that billing is weight-based per tool call, that new accounts start at US$0.25 and receive a US$3.00 monthly grant after confirmation plus 3 days, and that a next_step appears when the balance is low. This is substantive behavioral context an agent cannot get from the structured fields.

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 response contents are front-loaded in the first clause, which is good structure. The middle sentences carry a fair amount of pricing minutiae (unit weights, US$0.0005 per unit, plan allowances) that is useful for interpreting the returned cost table but is dense for a single paragraph.

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?

With no input parameters and no output schema, the description must carry the full burden of explaining what comes back, and it does: balance, cost breakdown, credit-by-expiry, history, top-up path, and the conditional next_step. An agent has enough to call this correctly and interpret the result without additional schema support.

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 tool takes zero parameters, so per the rubric the baseline is 4; there is no parameter semantics to clarify and the schema is empty. Nothing in the description adds or detracts from parameter understanding.

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 states a specific resource (the signed-in account's prepaid credit) and enumerates exactly what the response contains: balance, per-call costs, credit by expiry, recent history, and top-up guidance. It also names the sibling tool (add_credit) that handles the adjacent action, so an agent can distinguish this read-only balance check from the top-up operation.

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?

It explicitly routes the agent to add_credit for adding funds and notes that a low balance yields a next_step, which is actionable context. However, it never states when to prefer this over related account/history siblings such as my_history or supply_balance, so the routing is partial rather than exhaustive.

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