quickbooks_list_accounts

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

No annotations exist, so description carries burden. It implies a read-only list operation but does not explicitly state read-only behavior, permission needs, or other side effects. A basic list tool description, but adequate.

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?

Two clear sentences plus a concise parameter list. No unnecessary words, front-loaded purpose, efficient structure.

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 existence of an output schema, description does not need to explain return values. It covers purpose and parameters adequately. Minor gaps in pagination details, but overall complete for a list tool.

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?

With 0% schema description coverage, the description adds essential meaning to both parameters: 'account_type' as an optional filter, and 'max_results' as the maximum number to return. This compensates fully for missing schema descriptions.

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?

Clearly states it lists the QuickBooks chart of accounts for GL and statement analysis. The verb 'list' and resource 'chart of accounts' are specific and distinct from sibling list tools like quickbooks_list_bills.

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?

Identifies the use case (GL and statement analysis) but does not explicitly exclude alternatives or state when not to use. The resource name sufficiently differentiates from sibling tools.

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