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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value by previewing the payload (balance, prices, top-up guidance), but says nothing about freshness, currency, or whether prices are per-message rates — behavioral detail an agent would want for a billing read.

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?

A single tight sentence that front-loads the identity of the resource and then lists the returned fields. No filler, no repetition of the title.

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 parameters, no output schema, and read-only annotations, the description does the necessary work by enumerating what the response contains. It stops short of saying whether the balance is scoped to agent vs organization or what units prices are in, but it is close to sufficient for a simple getter.

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 schema is empty (0 parameters) with 100% coverage, so the baseline is 4. The description correctly implies no input is required, consistent with a no-arg wallet lookup.

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?

Names a specific verb and resource ('Returns the wallet') and scopes it to 'this agent spends from', which implicitly separates it from the org-level sibling org_billing_get. It also enumerates the returned contents (balance, prices, top-up instructions), but never names the sibling it differs from explicitly.

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 only implied: an agent can infer this is the pre-spend balance check, and the mention of 'how to top up' hints at a follow-up with billing_topup or topup_start. There is no explicit when-to-use, when-not-to-use, or named alternative vs org_billing_get, billing_transactions, or topup_status.

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