qb_account_balance

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the currency-scoping behavior, but says nothing about failure modes (unknown account) or whether the value is as-of-now or period-based.

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?

One tight sentence that front-loads the resource and appends the currency qualifier. Nothing is redundant, though the brevity comes partly at the cost of the missing parameter guidance.

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 and only one parameter, the description is nearly complete, but the unresolved format of the 'account' argument is exactly the information an agent needs before calling. It also does not say whether the balance is a point-in-time or period figure.

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?

Schema description coverage is 0% for the single required parameter 'account', which the description leaves ambiguous: it does not say whether this is an account ID, a fully qualified name, or a free-text name. The parenthetical examples clarify which kinds of accounts exist, not what value to pass.

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?

States a specific resource and scope: the balance of a single account, returned in that account's own currency. It distinguishes itself implicitly from list-style siblings like qb_list_accounts and qb_company_info, but never names an alternative explicitly.

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?

No when-to-use or when-not-to-use guidance, and no mention of prerequisites such as the account needing to exist or how to obtain the account identifier first. The agent must infer from the name that this is the single-account counterpart to qb_list_accounts.

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