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

Annotations already declare this as read-only, idempotent, non-destructive, and closed-world. The description adds meaningful context beyond that by identifying what balance is for and by explicitly saying payout account numbers are not returned, which is a useful data-boundary disclosure.

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, front-loaded, and each sentence contributes information. The final sentence 'No payout account numbers' is slightly terse and could be phrased more explicitly, but it still earns its place as a scope boundary.

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 zero-parameter read tool with strong annotations and no output schema, the description gives a reasonable sketch of the returned content: balance for calls plus withdrawable, pending, and paid earnings for experts. It stops short of describing currency or exact response shape, but the overall context is adequate.

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 has zero parameters, so the baseline is 4. The description does not need to explain parameter behavior, and nothing misleading is introduced.

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 (wallet balance), its purpose (used to pay for calls), and the extra earnings fields experts receive. It also sets a clear data boundary (no payout account numbers), though it does not explicitly distinguish itself from overlapping siblings such as get_earnings_summary or get_releasable_balance.

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?

Usage is implied by 'used to pay for calls' and by the mention of expert earnings, so an agent can infer when to call it. However, there is no explicit when-to-use versus alternatives guidance, which matters given several related balance, earnings, and payout tools.

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