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

Annotations already mark this as read-only and non-destructive, and the description adds substantial behavioral detail: it compares against all attachments, returns compact rows with a specific field list, orders newest first, reports documented/undocumented counts, and truncates oversized windows from the oldest end. This goes well beyond the annotation baseline.

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 well-organized: purpose first, then methodology, output shape, a practical caveat, and truncation behavior. Every sentence adds distinct value and there is no redundant or fluffy wording.

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 that there is no output schema, the description compensates by enumerating returned fields, ordering, counts, and truncation behavior. It also warns about legitimate receipt-free categories. Combined with complete schema parameter docs and safety annotations, nothing essential is missing for an agent to invoke this correctly.

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?

The input schema already describes all four parameters with 100% coverage. The description adds only that 'from' and 'to' limit the date range, which is already implied by the schema descriptions. It does not introduce new parameter meaning, so the baseline of 3 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: 'List purchases and bills with no document attached in QuickBooks.' It clearly distinguishes itself from sibling search tools like search_purchases and search_bills by focusing on missing attachments across two transaction types.

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 makes the tool's context clear: it is for finding expenses without receipts, and it adds a caveat that some categories may not require receipts. It does not explicitly name alternatives or say when not to use it, but the unique attachment-filtering purpose is evident from the description and name.

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