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

Annotations only supply readOnlyHint=true, but the description adds real behavior beyond that: it states the required scope ('Requires billing.read'), reiterates read-only with the mutation path for top-ups, and documents a non-obvious edge case ('never credited reads as absent, which is the free tier, not an empty wallet'). This is more than the annotations provide.

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?

Purpose is front-loaded in the first clause, and every subsequent phrase (state enumeration, absent-wallet semantics, scope requirement, mutation pointer) adds distinct information. The one expendable element, the CLI-twin aside, is minor.

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 output schema, the description carries the return-value burden and does so thoroughly, telling the agent what fields to expect (net EUR position, funding/grace/restricted/frozen state, ordered credit lots with expiry, top-up status) plus the absent-wallet interpretation. An agent has enough to call this correctly and interpret the result.

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 nothing for the description to clarify on the parameter side, and it correctly does not waste space inventing arguments.

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 names a specific resource (the organisation's prepaid credit wallet) and enumerates exactly what it reports: net position in EUR, funding state, credit lots with spend order and expiry, and top-up availability. It does not, however, differentiate from adjacent billing siblings such as get_billing_standing or get_usage, so it stops short of a 5.

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: the tool is framed as read-only and the note 'credit is added from the Billing page' steers the agent away from expecting a mutation here. There is no explicit statement of when to prefer this over get_billing_standing or other billing reads, which is a clear gap given the crowded billing sibling set.

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