qbo_items_list

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only mentions 'pagination' but does not disclose potential behavioral traits such as rate limits, data volume handling, sorting, or default ordering. The lack of any annotation and minimal description leaves significant gaps.

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 that efficiently states the purpose and key feature (pagination). No unnecessary words. It is front-loaded with the essential information.

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?

For a simple list tool with two parameters and no output schema, the description is largely complete. It could be improved by mentioning the returning format or explicitly noting that it retrieves all items if no filters are applied. However, given the low complexity, it is adequate.

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?

Both parameters (startPosition and maxResults) are fully described in the input schema (100% coverage). The description adds the word 'pagination' which contextualizes the parameters but adds little new meaning beyond the schema. Baseline score of 3 is appropriate.

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 'List Item records in QuickBooks Online with pagination', specifying the verb (list), resource (Item records), and context (QuickBooks Online). It differentiates from sibling tools like qbo_items_create, qbo_items_get, and qbo_items_search by being the dedicated listing operation.

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 all items, but does not explicitly state when to use this tool over alternatives like qbo_items_search or when pagination is needed. No guidance on exclusions or prerequisites is provided.

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