quickbooks_items

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

No annotations are provided, so the description carries full burden. It does not disclose important behavioral traits such as pagination behavior, rate limiting, required authentication (though access_token parameter exists), or what constitutes valid query syntax. The single sentence offers minimal insight into tool behavior.

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, which is compact but lacks any structure. While it avoids verbosity, it does not add additional context or break information into digestible parts. It is average in conciseness given the tool's complexity.

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?

With 6 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the query language for the 'where' parameter, the default limit/offset behavior, or the effect of sandbox mode. The agent would struggle to use this tool correctly without external documentation.

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 description coverage is 0%, meaning no parameter descriptions exist in the input schema. The tool has 6 parameters (including required access_token and realm_id, plus where, limit, offset, sandbox), but the description adds no meaning to any of them. The agent must infer semantics solely from names, which is insufficient for a query tool.

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 uses 'Query QuickBooks Online items (products and services)', which clearly specifies a verb and resource. It distinguishes from sibling tools like quickbooks_customers by naming the specific resource type (items) and clarifying it covers both products and services.

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 instead of alternatives. There is no mention of prerequisites, filtering contexts, or when the query parameter syntax would be appropriate. The description simply states what it does without usage direction.

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