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

Beyond the readOnlyHint annotation it discloses ordering (newest first), the exact returned fields, documented/undocumented counts, exclusion of charges flagged said_no_receipt, and truncation-from-the-oldest-end behavior. That is unusually rich behavioral context for a read tool.

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?

Purpose is front-loaded and most sentences carry distinct information (exclusions, return fields, truncation). It is somewhat dense with one long comma-separated sentence enumerating return columns, but little is wasted.

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 no output schema, the description does the heavy lifting by enumerating returned rows and counts, exclusions, ordering and truncation. Complete enough to call correctly; a note on pagination/limits would make it airtight.

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%, so the schema already documents to, from, types and company fully. The description only adds that from/to limit the date range and ties truncation to window width, which is marginal over the schema baseline.

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?

States a specific verb (List) and a precise scope (purchases and bills with no document attached in QuickBooks). This cleanly differentiates it from siblings like search_purchases, search_bills, search_attachables and list_purchases_without_payee.

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?

Gives clear context on the job (surfacing transactions missing receipts) and notes implicit exclusions such as payroll, tax remittances, transfers and bank fees that may not require receipts. It never names an alternative sibling or states an explicit when-not-to-use, so it stops short of the top score.

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