qbo_accounts_list

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

With no annotations provided, the description solely carries the burden of behavioral disclosure. It only mentions pagination, omitting details on error handling, rate limits, or behavior when no results are found.

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?

Single sentence, no wasted words. Could benefit from slight expansion to include usage context, but remains efficient and front-loaded with the core action.

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 comprehensive parameter schema, the description is minimally adequate. However, it lacks details on return format, error conditions, and how it differs from similar tools like qbo_accounts_search.

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% (both parameters described in the schema). The description adds the term 'pagination' but does not enhance understanding beyond the schema. Baseline 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 'List Account records in QuickBooks Online with pagination' clearly states the verb 'List' and resource 'Account records'. It differentiates from create/update/get/search siblings by the verb, but does not explicitly distinguish from qbo_accounts_search, which could cause confusion.

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 on when to use this tool versus alternatives like qbo_accounts_search (which likely supports filtering) or qbo_accounts_get (for a single record). The description lacks context for appropriate usage scenarios.

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