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

The top-level description adds no behavioral traits beyond what the annotations already provide: it merely says the tool searches records. Important behaviors like no-OR filtering, one-page-at-most-1000 truncation, case sensitivity, and inactive-record exclusion are present only in the criteria parameter description, not in the tool description.

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 a single, front-loaded, waste-free sentence: 'Search department records in QuickBooks Online.' It is concise and easy to parse, though it is brief enough that it omits useful behavioral context that would make it genuinely helpful.

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?

The detailed criteria schema makes the definition minimally viable, but with no output schema and no tool-level mention of pagination, default inactive filtering, or the get_department alternative, an agent must infer important invocation context. It is adequate but has clear gaps.

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%, with the criteria parameter already explaining operators, ANDed filters, pagination, and inactive-record behavior. The tool description adds no parameter-level meaning, so the baseline score of 3 applies.

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 names a specific verb and resource: 'Search department records in QuickBooks Online.' It is clear about what the tool does, but it does not differentiate this tool from the sibling get_department or other search_* tools, so it falls short of a 5.

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 gives no guidance on when to use this tool versus alternatives such as get_department. It does not state exclusions, prerequisites, or recommended use cases; the only substantive usage detail lives inside the criteria parameter schema, not in the tool description.

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