Accounts Get Historical Balances

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

The description adds no behavioral insights beyond the annotations (readOnlyHint, openWorldHint, idempotentHint). It fails to disclose details such as that it returns balances for specified accounts at a single date, or any constraints like the maximum date range. No contradiction with annotations.

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 one-sentence description is overly terse, bordering on useless. It lacks structure and essential detail, achieving brevity at the expense of clarity.

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?

Given the tool has 5 parameters, no output schema, and operates within a complex domain (account balances), the description is critically incomplete. It omits what data is returned, how filtering works, and the meaning of 'historical'.

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?

With only 40% of parameters having descriptions in the schema, the tool description must compensate but does not. It offers no additional meaning for parameters like 'filters' or 'balance_date', leaving the agent to infer from names alone.

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 'Get historical balances' is a tautology of the tool name and title. It fails to specify that it retrieves account balances at a past date, nor does it distinguish from sibling tools like accounts_get_account_history or accounts_get_net_worth_breakdown which also deal with historical financial data.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or exclusions, leaving the agent without context for correct selection.

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