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

The annotations already declare readOnlyHint=true and destructiveHint=false, and 'Search' is consistent with that. However, the description itself adds no behavioral context beyond the annotations: it does not mention pagination, truncation, inactive-vendor exclusion, or query limitations. Those behaviors are present only inside the parameter schema, not in the 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 sentence with no filler, no repetition of the tool name, and the action plus resource are front-loaded. It is appropriately compact for a read-only search tool whose parameter complexities are handled by the schema.

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 overall definition is usable because the schema documents criteria grammar, pagination guidance, and company disambiguation, while annotations confirm a safe read operation. However, there is no output schema and the description never states the response shape or that output is a page of matching vendor records. This leaves an agent to infer what the tool returns.

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 both company and criteria parameters documented; the criteria description is especially detailed about operators, AND semantics, and QBO limitations. The top-level description adds no parameter-level meaning, so the baseline score of 3 for high schema coverage 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 states a specific verb and resource: 'Search vendor records in QuickBooks Online.' This clearly tells an agent what the tool does and distinguishes it from sibling tools that search other QBO entities such as search_customers or search_invoices.

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 provides no guidance about when to use search_vendors versus get_vendor, get_vendor_balance, search_vendor_credits, or other related tools. It does not state conditions, exclusions, or mention that criteria-based searching is the differentiator. Useful usage context lives only in the schema's criteria description, 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.