hcloud_show_bss_account_balance

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing beyond the acronym expansion: it does not say whose account is queried, whether the call is scoped to the caller's credentials, what the balance comprises (credit, cash, arrears) or what form the value takes, which matters given openWorldHint signals an external billing system.

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 short phrase with the action verb front-loaded and the acronym expanded inline; there is no padding or redundant restatement 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?

For a zero-parameter read with no output schema, the description is minimally adequate: it names the resource but leaves the return shape undefined, since with no output schema the agent has no way to know whether it receives a numeric amount, a currency code, or a breakdown. It is sufficient to select the tool but thin on what to expect back.

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 and the schema is an empty object, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 gives a specific verb ('Show') plus a specific resource ('BSS account balance') and expands the BSS acronym to Billing and Subscription, so an agent knows exactly what it retrieves. It does not explicitly distinguish itself from the billing-adjacent siblings hcloud_list_bss_customer_orders and hcloud_list_bss_measurements, but the resource noun 'balance' is unique enough among them that confusion is unlikely.

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?

There is no when-to-use guidance, no statement of prerequisites, and no reference to any alternative tool or fallback. The agent must infer from the name alone that this is the tool for balance queries and that the BSS list siblings cover orders and measurements instead.

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