quickbooks_list_purchases

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

Without annotations, the description should disclose behavioral traits (e.g., what data is retrieved, pagination, side effects). It only provides routing details (JWT, tenant, company scope) but does not explain the actual behavior of listing purchases, such as whether it is read-only or what entities are returned.

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 succinct, but the first sentence is slightly redundant (repeating the name and platform tool). The routing information is placed upfront but could be integrated more efficiently. Overall, it is acceptable but not optimally structured.

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 complexity of QuickBooks and many sibling tools, the description lacks essential context. It does not explain what constitutes a 'purchase' in QuickBooks, nor does it describe the output even though an output schema exists. The agent is left with insufficient information to correctly use or interpret results.

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 must compensate. It states 'arguments: JSON string of arguments for the connector operation' but does not specify what fields or structure the JSON should contain. This adds minimal meaning beyond the raw schema.

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 identifies the tool as a QuickBooks connector for listing purchases, and the name 'list_purchases' clearly indicates its function. However, it does not differentiate this from sibling tools like quickbooks_list_bills or quickbooks_list_invoices, which are similar listing operations for different entities.

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 provides no guidance on when to use this tool versus other listing tools (e.g., quickbooks_list_bills). It does not mention prerequisites, context, or alternatives, leaving the agent without decision support for tool selection.

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