balance_sheet

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

Description discloses that it computes cumulative balances from posted journal items only, and uses a specific as_of_date cutoff. Given no annotations, this provides useful behavioral context, but it does not mention return format or any permissions/errors.

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?

Single sentence, front-loaded with the report name, and packs essential details without unnecessary words.

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?

The description covers the report's purpose, date scope, and data source (posted items), which is adequate for a simple read-only report. However, it omits behavior for optional company_id and does not describe the output structure, though that may not be critical.

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?

Schema has no parameter descriptions and description covers only the as_of_date parameter (cumulative up to that date). The optional company_id parameter is not explained in the description, leaving its semantics unclear.

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?

Description clearly identifies the tool as generating a balance sheet (assets/liabilities/equity) as of a specific date, distinguishing it from sibling reports like profit_and_loss. It specifies the source (posted journal items) and computation method (cumulative balances).

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 use for balance sheet reporting but does not explicitly state when to use this over sibling reports like trial_balance or profit_and_loss. There are no exclusion criteria or alternative references.

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