get_money_report

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

No annotations are provided, so the description carries the transparency burden. It discloses the data scope (current balances, bank accounts, cash registers, RUBLES) but does not mention return format, data freshness, permissions, or any limits. It adds useful context but remains minimal.

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?

Two short, front-loaded sentences convey the tool's purpose and currency scope with no wasted words. The key information is immediately available.

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 report tool, the description adequately covers what data is returned and how it is grouped. The lack of an output schema leaves a minor gap around the exact return structure, but the core purpose is complete.

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 has zero parameters and 100% coverage, so there is no parameter burden on the description. The baseline of 4 applies because no parameter meaning is needed; the description confirms the tool requires no inputs.

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 clearly states the tool retrieves current money balances, grouped by bank account and cash register, with currency specified as RUBLES. This is specific and distinguishes it from sibling report tools like profit or sales reports.

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?

Usage context is implied: use this when you need current balances across accounts and registers. However, there are no explicit alternatives, exclusions, or when-not-to-use guidance relative to sibling cash/report tools.

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