audit_balance_sheet

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing: not whether the check is a read-only validation, what rules are applied, what errors or flags result, or what happens with malformed input. An agent cannot predict behavior at all.

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 three-word phrase is terse but this is under-specification rather than conciseness; there is no front-loaded purpose or scope to anchor the call. Brevity here costs rather than earns.

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 a nested-object parameter with zero schema coverage, no annotations, and no output schema, the description needs to explain input shape and audit behavior and does none of it. It is wholly inadequate for even the minimum viable call.

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 description coverage is 0% and the single parameter is a nested object keyed by string with numeric values, which is entirely undocumented. The description adds no meaning about expected keys (e.g., account names, amounts) or structure, leaving the agent unable to construct a valid call.

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?

'Audit balance sheet' is a bare restatement of the tool name with no elaboration. It identifies a verb and resource, but gives no hint of what an 'audit' checks, what the balance_sheet_dict should contain, or how it differs from siblings like audit_income_statement or audit_cross_footing.

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 indication of when to use this tool versus audit_income_statement, audit_cross_footing, or run_benchmark_financial_audit. No prerequisites, no input format expectations, no exclusions.

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