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

The description goes beyond the readOnlyHint/destructiveHint annotations by detailing the return structure (columns, column_types, rows), row types, id semantics, hidden_zero_rows, filters, and no_data flag. This gives the agent significant behavioral insight, though it could mention potential size of results or any caveats about performance, which is minor.

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 packed with essential information. It front-loads the core purpose and return structure, then provides detail on edge cases. While it's long, every sentence provides value, and the structure is logical, though it could be slightly more streamlined.

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?

Given the tool's complexity (nested objects, no output schema), the description comprehensively explains the return format, edge cases (all-zero rows), and filtering behavior. It covers everything an agent needs to interpret the results correctly, making it complete for its purpose.

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 schema has near-complete coverage of parameters with descriptions of date options, field lists, and company selection. The description does not add additional parameter-level details beyond what's in the schema, so a baseline score of 3 is appropriate given the high schema coverage.

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 clearly states that it generates the QuickBooks open invoices report, using a specific verb ('generate') and a specific resource ('QuickBooks open invoices report'). It distinguishes itself from sibling tools like search_invoices and get_invoice by focusing on the report format rather than individual invoice retrieval.

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 for reporting scenarios, and the detailed explanation of report structure and filters helps an agent understand when to use it. However, it does not explicitly state when NOT to use it or direct to alternatives like search_invoices for non-report needs, leaving some ambiguity.

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