quickbooks_list_items

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

No annotations provided. The description mentions routing through an API endpoint but does not disclose whether the tool is read-only, has side effects, or requires specific permissions.

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 short but includes routing details that may be better placed elsewhere. Still concise, but not optimally structured for quick comprehension.

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 large set of sibling list tools and lack of annotations, the description is severely incomplete. It does not explain what data is returned, how to filter, or when this tool is appropriate.

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?

The single parameter 'arguments' is described as a 'JSON string of arguments for the connector operation', which adds little beyond the schema (default '{}', type string). With 0% schema coverage, the description fails to explain valid argument structures.

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 only states 'list_items' without specifying what kind of items (e.g., inventory, products, services). It relies on the tool name and sibling context, but the text alone is vague.

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 quickbooks_list_accounts or quickbooks_list_invoices. No context about prerequisites or scope.

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