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

The description goes well beyond the readOnlyHint/destructiveHint annotations by disclosing the exact return shape, row types, Money cell representation, id alignment behavior, omission of all-zero rows with hidden_zero_rows count, filter confirmation semantics, and no_data flag. This is rich behavioral context that an agent needs to interpret the response correctly.

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 and information-rich, front-loading the report generation purpose before diving into return-format details. Every sentence adds value, though the long run-on sentence about return structure could be slightly better organized. It is appropriately sized for the complexity of the output format.

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?

For a read-only report tool with no output schema, the description is remarkably complete: it explains the return structure, row types, value alignment, id behavior, zero-row handling, filter confirmation, and no-data signaling. The parameter schema covers all inputs. Nothing an agent needs to call this tool and interpret its response 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 all parameters. The description adds context about how filters appear in the response (filters lists confirmed filters, ignored parameters are absent), which helps understand parameter behavior, but it does not add syntax or format details beyond the schema. Baseline 3 is appropriate.

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 resource ('QuickBooks vendor balance detail report'), and the detailed return-format explanation distinguishes it from sibling report tools like get_vendor_balance, get_aged_payable_detail, and get_vendor_expenses. It clearly identifies what the tool produces and how the output is structured.

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 description implies usage context by naming the report type and listing filter parameters, but it does not explicitly state when to prefer this over sibling report tools (e.g., get_vendor_balance vs get_vendor_balance_detail). The parameter schema provides the filter options, but there is no explicit when/when-not guidance or alternative tool names.

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