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

With no annotations, the description carries the full burden and delivers: default resolution, 404 vs 422 error semantics, the double-counting hazard, and the fiscal_year_id vs posting-date cut distinction. It stops short of auth/permission needs or rate limits.

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 core scoping statement is front-loaded and dense with useful facts, but the final paragraph about cut semantics is convoluted, and internal ticket references (ZET-155, ZET-166) are noise that consume space without helping an agent invoke the tool.

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?

With no output schema and no annotations, the description supplies the return shape at a high level (columns plus totals), error behavior, and cut semantics. It is nearly sufficient, missing only detail on the exact column set and whether totals are included per account or only overall.

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 coverage is 0%, so the description must compensate and largely does: fiscal_year is a year label defaulting to the latest posted year, period_id narrows within that year, and account identity is the (company, fiscal year, code) tuple. It never states the accepted type/format for company_id or period_id, leaving some gaps for a 0%-coverage schema.

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 opening clause names a specific verb/resource pair: per-account debit/credit columns for one fiscal year with totals. It differentiates itself from the financial-statements path by cut semantics, but does not address how it differs from gl_balance_sheet or get_gl_account_ledger, which an agent could plausibly confuse with a trial balance.

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?

It explains that fiscal_year defaults to the latest posted year, that period_id narrows to one period, and explicitly warns there is no all-years mode because aggregation double-counts. It also names a contrasting path (…/financial-statements) and when the two diverge. No explicit 'use this instead of X' routing to the other GL tools.

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