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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds genuinely new context: the credential source is the connection's HTTP header rather than a parameter, and the call is free. It still doesn't describe what a balance value looks like or any rate limits, keeping it out of 5 territory.

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 sentence that front-loads the operation and the credential source, with no redundant restatement of the title or name.

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 no-parameter, read-only tool with full schema coverage and no output schema, the description covers the essentials: what it returns (a balance), how it authenticates, and that it is free. It could say more about the relationship to create_credit_checkout, but no critical calling information 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?

Zero parameters means the schema has nothing to explain, and the description correctly notes that no key argument is accepted, preempting an agent from trying to pass one. That is the only meaningful semantic point for this tool.

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 operation (balance check) and the exact resource it reads (the API key in this connection's HTTP header), which is more precise than the title alone. It does not explicitly distinguish itself from siblings like create_credit_checkout, 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?

Mentioning that the check is 'free' implies it is a safe, low-cost call, and 'takes no key argument' clarifies the invocation contract. However, it never states when to prefer this over create_credit_checkout or what to do when the balance is low, so usage guidance is only implied.

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