search_bill_payments

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure and largely drops it. It never states that this is a read-only operation, how pagination works (limit/offset/fetchAll exist in the schema but are unexplained), what the result set looks like, or whether fetchAll can be expensive — all material for an agent deciding how to page through bill payments.

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?

It is a single front-loaded sentence with no filler, which is efficient. The brevity is achieved through omission rather than compression, but the sentence itself reads cleanly.

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 zero annotations, no output schema, and a nested params object with 0% description coverage, the definition should explain at minimum pagination behavior and the criteria format. None of that is present, so an agent cannot confidently construct a query or predict the response shape from this description alone.

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 0% on a nested params object containing criteria, asc, desc, limit, offset, count, and fetchAll. The description's only parameter-adjacent text is 'match given criteria,' which adds no syntax, field names, or format information beyond what the schema already implies, leaving every sub-parameter's meaning undocumented.

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 ('Search') and resource ('bill payments in QuickBooks Online'), so the operation is unambiguous. It does not distinguish this tool from nearby siblings such as search_bills, search_payments, or get_bill_payment, leaving the agent to infer which resource type is correct.

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?

There is no guidance on when to use this instead of search_bills (the underlying bills) or search_payments (payments in general), nor any stated prerequisite such as needing a bill ID or date range. The only usage cue is the phrase 'match given criteria,' which restates the name rather than routing the agent among alternatives.

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