quickbooks_invoices

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

No annotations provided, so description carries full burden. It mentions create (mutation) but lacks details on side effects, permissions, rate limits, or error states. The description is too vague to inform the agent about behavioral traits beyond the basic actions.

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, making it concise but lacking substance. It front-loads the verbs, but it is too brief to provide meaningful guidance for the complex tool.

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 no output schema, no annotations, 9 parameters with many undocumented, and nested objects, the description is severely incomplete. The agent lacks critical information about return format, authentication, and parameter usage for a tool of this complexity.

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 only 33%. The description adds no additional meaning beyond the schema; it merely restates parameter names. For critical parameters like 'where', 'limit', 'offset', and 'sandbox', no explanation is given, leaving the agent without sufficient understanding.

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?

Description clearly states the tool can list, get, or create QuickBooks Online invoices, specifying the resource and actions. However, it does not differentiate from sibling QuickBooks tools like quickbooks_customers or quickbooks_payments, which also operate on different resources.

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, no prerequisites mentioned, and no context for when this tool is appropriate. The description simply lists available actions without usage context.

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