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

The annotations already declare readOnlyHint=true, and the description's 'Check' wording is consistent with that. The description adds useful context beyond the annotations by specifying that the balance is 'current' and tied to the 'authenticated user,' implying a live account-scoped read with an authentication precondition.

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 a single, efficient sentence that states the action, the resource, and the scope without wasted words. Every phrase adds meaning.

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-only balance check, the description is nearly complete: it identifies what is being checked, whose balance it is, and that it reflects the current state. It does not describe the return format, but the tool's simplicity and read-only annotation make this a minor omission rather than a blocking gap.

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 of 4 applies. There is no parameter meaning for the description to add, and the input schema already fully covers this by having an empty properties object.

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 uses a clear verb ('Check') and a specific resource ('current credit balance') scoped to the authenticated user. It is immediately distinguishable from the sibling tools, which all deal with brand names, deep dives, or research rather than account credits.

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?

The description clearly establishes the use case: checking the authenticated user's current credit balance. It does not explicitly name alternatives or exclusions, but no sibling tool covers credits, so the intended context is unambiguous and no wrong sibling could plausibly be selected.

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