search_bills

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

No annotations are supplied, so the description carries the full behavioral burden and it delivers almost nothing: it does not state that the operation is read-only, how pagination (limit/offset/count) behaves, what fetchAll does to result size, or whether results are capped. The word 'Search' implies a non-mutating read, but that is inference rather than disclosure.

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?

A single short sentence with no filler and the resource front-loaded, so nothing is wasted. However, the brevity reflects under-specification rather than disciplined concision for a tool with seven nested optional parameters.

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 a deeply nested params object, no annotations, no output schema and no description of pagination or result shape, the definition leaves the agent guessing about how to page, sort, or bound the result set. For this level of schema complexity, one sentence is not sufficient.

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% at the top level: asc, desc, count, limit, offset, criteria and fetchAll are all undocumented in the description. The nested schema does inline-describe the criteria field/operator and the simple {key,value} legacy form, which prevents a lower score, but the description itself adds no meaning about sorting, paging or fetchAll semantics.

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 gives a specific verb and resource ("Search bills") plus the system context (QuickBooks Online), which distinguishes it from get-bill, create-bill, update-bill and delete-bill in the sibling list. The only shortfall is that it does not explicitly contrast itself with read-style retrieval or state what 'criteria' means at a high level.

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 choose search_bills versus get-bill (fetch one by Id) or versus listing through another endpoint. No prerequisites, no note that at least one criterion or a fetchAll flag is typically needed, and no exclusions.

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