quickbooks_create_invoice

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

No annotations are provided, so the description bears full responsibility. It mentions 'draft' but does not explain behavioral traits such as saving state, required permissions, side effects, or the format of the output (though an output schema exists but is not described). The description is insufficient for the agent to understand the tool's 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 short and includes a structured args list. It is concise but could be slightly improved by aligning with the schema and adding usage context. No extraneous information.

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 annotations and a 0% schema description coverage, the description is incomplete. It lacks details on output, error handling, prerequisites, and the correct format for line_items. The mismatch between description and schema further degrades completeness.

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 description adds some meaning to parameters (e.g., 'QuickBooks customer ID' for customer_id, 'YYYY-MM-DD' format for due_date), but the schema coverage is 0%, so it must compensate. However, it incorrectly describes line_items as 'JSON-string list' while the schema expects an array of strings, creating a mismatch. The claimed required status contradicts the 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 clearly states the action ('Create') and the resource ('draft QuickBooks invoice for a customer'). It implies the tool is for invoice creation, which differentiates it from other QuickBooks tools like list_invoices or create_bill, though no explicit distinction is made.

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 (e.g., quickbooks_create_bill for bills, square_create_invoice for Square). The description contradicts the input schema by stating customer_id and line_items are required, while the schema marks them as optional with default null, potentially misleading the agent.

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