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

Annotations already declare readOnly, idempotent, non-destructive behavior, and the description adds real value on top: the wallet ledger is authoritative ('from the app ledger'), a review_required wallet cannot spend, the call is free, and purchases stay in the Brix36 app. It stops short of describing pagination or failure modes, but those are largely irrelevant for a zero-param 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?

Three short sentences, front-loaded with the core action and the returned fields, then the review/spend caveat, then cost. No filler, though the trailing 'purchases remain in the Brix36 app' is the weakest sentence and slightly off-topic.

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?

An output schema exists and annotations carry the safety profile, so the description only needs to establish scope and the key caveat — which it does. For a zero-parameter read tool, nothing needed to call it correctly is missing.

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 the baseline is 4 and schema coverage is 100% with nothing to document. The description correctly adds no parameter claims that could conflict.

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 verb and resource ('Read the connected customer wallet') and enumerates the returned balance fields, so an agent knows exactly what this retrieves. It does not explicitly distinguish itself from the closest sibling, studio_credit_usage_list, leaving that inference to the reader.

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 rather than stated: the agent can infer this is the tool for checking spendable credit before a generation. The 'Free' note gives cost context, but no when-to-use/when-not conditions or named alternatives (e.g., credit usage history) are provided.

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