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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the trailing 'Read-only' is redundant. The genuinely additive part is the accounting behavior: equity includes net income to date so the sheet always balances, which preempts an agent misreading the retained-earnings figure. It still says nothing about permissions, behavior for periods with no closed books, or how missing parameters default.

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 tightly packed sentence with the primary output (assets, liabilities, equity) front-loaded before the balancing caveat. No filler, though the leading 'GetBalanceSheet' restates the tool name and the description is arguably too terse given the undocumented parameters.

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?

An output schema exists, so return-shape explanation is not owed here, and the read-only profile is covered by annotations. What remains missing for a 4-parameter financial report tool is any guidance on basis selection and date/currency defaults, which the description does not supply.

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 only 25% — just the companyId UUID wrapper is documented. The description implies asOfDate via 'as of a date' but never explains basis (REPORT_BASIS_ACCRUAL vs CASH vs UNSPECIFIED), what UNSPECIFIED defaults to, or what currencyCode falls back to; the accrual/cash distinction materially changes the numbers and is left entirely to the enum names.

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?

States a specific verb and resource (returns assets, liabilities, equity balances as of a date), which is more precise than the title alone. However, it does not differentiate itself from near-identical siblings such as accounting_get_trial_balance, accounting_get_profit_and_loss, or accounting_get_statement, leaving the agent to infer which report to pick from the account hierarchy.

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 explicit when-to-use or when-not-to-use guidance and no reference to alternative report tools. The only implicit cue is 'as of a date,' which hints at point-in-time reporting but never states the condition that selects this tool over the trial balance or cash flow statement.

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