search_bills

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

With no annotations, the description should disclose behavioral traits. It only says 'search bills that match given criteria,' omitting details about pagination (limit, offset), sorting (asc, desc), fetchAll, count, and company parameter. The complex criteria structure is not explained.

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, which is concise but lacks structure. It does not front-load important information like search capabilities or typical usage.

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 the complex schema (nested criteria, multiple pagination parameters) and no output schema, the description is incomplete. It does not explain return values, pagination behavior, or how to use criteria effectively.

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 low (approx. 29% of top-level parameters described). The description adds no parameter semantics beyond what the schema already provides, missing explanations for limit, offset, asc, desc, fetchAll, count.

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 clearly states the tool searches bills in QuickBooks Online with criteria, which distinguishes it from other search tools for different entities. However, it could be more precise about the nature of the search (e.g., listing bills) rather than a generic 'search'.

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?

No guidance is provided on when to use this tool versus alternatives like get-bill for a single bill or other search tools. The description lacks context about typical use cases or exclusions.

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