freeagent_get_trial_balance_opening

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 and the bar is lower. The description adds nothing behavioral beyond that—no indication of which period/date the opening balances correspond to, whether results are scoped to a company, or what happens when no opening balances exist.

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 sentence with the resource front-loaded and no filler. It is efficient, though its brevity is partly the source of the ambiguity rather than a virtue in itself.

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 tool this needs to explain the relationship to the trial balance and opening balances siblings and what period is implied, and it does neither. The agent has enough to attempt a call but not enough to choose it confidently over two similarly named tools.

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, so there is nothing for the description to disambiguate; the baseline of 4 applies. It correctly implies no filtering inputs are needed.

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 resource (trial balance opening balances) with the verb "Get," so the basic purpose is legible. However, it does nothing to distinguish this tool from its very close siblings freeagent_get_trial_balance and freeagent_get_opening_balances, leaving the agent guessing how the three differ.

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 guidance on when to use this instead of freeagent_get_trial_balance or freeagent_get_opening_balances, nor any stated preconditions (e.g., accounting period or company scoping). The agent must infer selection from the name alone.

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