kontist_get_balance

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

No annotations are provided, so the description carries the burden of disclosing behavior. 'Return' clearly signals a read-only operation, and it specifies the returned fields (balance, IBAN, available balance) and currency (EUR). It does not discuss authorization or error conditions, but for a simple balance getter this is reasonably transparent.

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 sentence with no filler. It front-loads the verb and then lists the exact return values, making it efficient and easy to parse.

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 balance lookup with no output schema, the description fully covers what an agent needs: what is returned (balance, IBAN, available balance) and the currency. No additional context seems necessary for correct invocation.

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 and the schema confirms this, so there is nothing for the description to add about parameter meaning. This matches the baseline for parameterless tools.

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 specific verb ('Return') and precise resource ('current Kontist business account balance, IBAN, and available balance'), making the tool's function immediately clear. It is naturally distinguished from siblings like kontist_list_transactions and kontist_get_tax_reserves because it focuses on balance and account identifiers.

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 intended use is implied by the description: call this tool when the current account balance or IBAN is needed. However, there is no explicit guidance on when not to use it or which sibling tool to prefer in alternative scenarios (e.g., tax reserves vs. account balance).

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