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

Annotations already signal read-only safety, but the description goes well beyond that by disclosing return shape, row types, the meaning of id, the difference in id alignment between summary and detail reports, hidden all-zero rows, filters QuickBooks actually applied, and the no_data flag. These are meaningful behaviors an agent would otherwise have to guess.

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 description is dense but every sentence carries necessary information. It front-loads the core purpose and then packs return-format details into a compact, structured set of clauses with no filler or repetition.

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, the description carries the full burden of explaining return values, and it does so thoroughly: columns, row types, depth, value alignment, ids, hidden_zero_rows, filters, and no_data. Nothing essential for correctly invoking and interpreting this report tool is missing.

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 100%, so the schema already documents start_date, date_macro, accounting_method, summarize_column_by, filters, and company. The description adds no parameter-level detail beyond mentioning the filters field as part of the return object, so it earns the baseline score.

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 states a specific verb ('Generate') and a specific resource ('the QuickBooks balance sheet summary report'). It clearly identifies this as the summary variant, and even contrasts summary-report behavior with detail-report behavior, differentiating it from siblings like get_balance_sheet_detail.

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 tool's purpose as the summary version of the balance sheet is clear, and the mention of 'summary reports' vs 'detail reports' implies when each variant applies. However, it never explicitly says 'use this for summaries, use get_balance_sheet_detail for detailed line-item data,' so the usage guidance remains implicit rather than explicit.

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