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

Beyond the readOnlyHint annotation, the description discloses important runtime behaviors: all-zero rows are omitted and counted in hidden_zero_rows, filters lists only the filters QuickBooks confirmed applying (ignored parameters are absent), and no_data indicates an empty period. This gives an agent reliable expectations for parsing and interpreting results.

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 each sentence carries meaningful detail about return structure, row semantics, hidden rows, filter confirmation, and no_data. It is not a short one-liner, but the complexity of the output deserves this level of specificity; the key purpose is front-loaded and the details are logically ordered.

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 present, the description fully compensates by documenting the complete return shape: columns, column_types, rows with type/depth/values, id alignment, hidden_zero_rows, filters, and no_data. For a report-generation tool with rich output and many sibling report tools, nothing essential is missing for correct invocation and interpretation.

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 100%, so the parameters are already documented in the schema. The description adds value by explaining that the filters parameter may not appear in the output if QuickBooks ignored it, and it clarifies how values and ids map differently between summary and detail reports. This goes beyond the raw schema definitions.

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 opens with a specific verb and resource ('Generate the QuickBooks profit and loss detail report') and consistently uses 'detail' to distinguish it from the sibling summary tool get_profit_and_loss. The report structure is also named explicitly, so an agent can tell exactly what this tool produces.

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 use for detailed P&L reporting, and the mention of 'summary reports' hints that a summary variant exists, but it never explicitly says when to choose this tool over get_profit_and_loss or other report tools. There is no direct exclusion or alternative routing; the agent must infer usage from the 'detail' naming.

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