qbo_sales_receipts_list

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions listing records but does not indicate whether the operation is read-only, any authentication requirements, rate limits, or whether results are sorted. This is insufficient for a list 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?

The description is a single sentence of 12 words, front-loaded with the key action and resource. No unnecessary words or information, achieving high conciseness.

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 absence of an output schema, the description should indicate what the response contains (e.g., list of SalesReceipt objects) but does not. It also omits default sorting behavior or any indication of result size limits. The tool has moderate complexity with 4 optional parameters, and the description is incomplete for making an informed invocation.

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 coverage is 100%, and the description adds the terms 'pagination' and 'TxnDate range' which align with parameters. However, the schema already describes each parameter adequately (e.g., default values, format). The description adds little meaning beyond what the schema provides, justifying the baseline score of 3.

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 verb 'List', resource 'SalesReceipt records', and context 'QuickBooks Online with pagination and optional TxnDate range'. It effectively distinguishes from sibling tools like qbo_sales_receipts_create, _get, _update.

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 implies usage for listing sales receipts with pagination and date filters, but does not explicitly state when to use this tool versus alternatives like qbo_sales_receipts_search or other list tools. No when-not-to-use or prerequisite information is provided.

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