quickbooks_list_purchase_orders

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

The description mentions routing through the API under JWT, tenant, and company scope, providing limited security context. However, it does not disclose whether the operation is read-only, if there are side effects, rate limits, or any other behavioral traits. With no annotations, this is a significant gap.

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 (3 sentences) but includes redundant information (repeating the tool name) and lacks prioritization of critical usage details. It is adequately concise 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 that the output schema exists, the description does not need to explain return values, but it still fails to describe how to use the 'arguments' parameter effectively or provide examples. The tool's complete dependency on a hidden connector API makes the description insufficient for an agent to invoke it correctly.

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 schema has 0% description coverage for the single 'arguments' parameter. The description only says it is a JSON string of arguments but provides no indication of valid keys, structure, or defaults beyond the empty object. This fails to compensate for the lack of 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?

The description states it's a QuickBooks connector operation for listing purchase orders. The verb and resource are implied by the name and clarified by the first sentence. However, it doesn't add specific scope or differentiation from siblings, though no sibling duplicates this exact function.

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 is provided on when to use this tool versus other QuickBooks tools or alternative methods. There are no conditions, prerequisites, or exclusions mentioned.

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