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

Annotations already mark the tool readOnly and non-destructive, and the description goes well beyond them. It documents the full return contract: row type/depth semantics, Money cells as numbers, id alignment for summary vs detail reports, hidden_zero_rows, confirmed applied filters, and no_data. There is no contradiction with the annotations.

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?

Two sentences with no filler; the purpose is front-loaded and the dense second sentence packs only high-value behavioral facts. It is not perfectly scannable due to the long semicolon-heavy structure, but every clause earns its place.

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 serves as the sole documentation of the return value and covers its important quirks: row types, value alignment, id semantics, hidden zero rows, filter confirmation, and no_data. Input parameters are fully covered by the schema, so nothing essential is missing for correct invocation.

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?

The input schema documents all parameters at 100% coverage, so the baseline is 3. The description adds one valuable parameter-related behavior: the returned filters array only includes parameters QuickBooks actually applied, so an absent filter means an ignored input. It avoids restating parameter formats already covered by the 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 description states a specific verb+resource: 'Generate the QuickBooks general ledger report.' It clearly identifies the exact report and the returned object shape. However, it never contrasts with the many sibling report tools (e.g. get_journal_report, get_trial_balance), so differentiation relies on the report's name rather than explicit scoping.

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 when-to-use or when-not-to-use guidance and no reference to alternative report tools. Given the large sibling set, an agent must infer from the tool name alone when to pick this instead of get_journal_report or get_transaction_detail_by_account. This is the clearest gap in the definition.

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