Get column balance

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the endpoint path and reinforces that this is a report retrieval. No behavioral surprises are disclosed, but none are needed beyond the annotations; no contradiction exists.

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 compact and the substantive sentence is helpful, but it opens with a redundant 'Get column balance.' that duplicates the title. The endpoint line is useful, though the first sentence could be removed without losing value.

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 read-only report tool with fully documented parameters and safety annotations, the description is functionally complete for invoking the tool correctly. It lacks explicit return-format information, but no output schema exists and the agent can still call it successfully based on the provided details.

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 input schema provides descriptions for all six parameters, including ranges and the administration enum, so schema description coverage is 100%. The description only restates that the report uses year, period range, and ledger account range, adding no meaningful detail beyond what the schema already provides.

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 'Get' and identifies a specific resource: a column balance (proef- en saldibalans) filtered by year, period, and ledger account range. It accurately describes the operation and is not a tautology, but it does not explicitly differentiate itself from the sibling get_balance_report tool.

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 implies usage when a column balance report is needed for given year, period range, and ledger account range. It provides no explicit guidance about when to choose this tool over alternatives such as get_balance_report, and no exclusions or alternative conditions are mentioned.

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