create_invoice

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

No annotations are provided, so the description must convey behavioral traits. It only states a generic creation action, omitting critical details like idempotency, side effects (e.g., does it affect inventory?), required permissions, or default behaviors (e.g., date handling). This is insufficient for an agent to understand the tool's operational consequences.

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 extremely concise at one sentence, which is efficient but sacrifices essential information. It is front-loaded with the main action, but brevity here undermines clarity and completeness, making it minimally acceptable.

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 tool's complexity (nested parameters, no output schema, no annotations), the description is severely incomplete. It fails to explain the overall workflow, success/error expectations, required vs optional fields, or any post-condition behavior. An agent would lack the context to use this tool reliably.

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 low (50% from context, only the 'company' parameter has a description). The description does not explain any parameters, leaving the agent to infer meanings from parameter names alone. For nested objects like 'line_items,' the schema provides types and constraints but no semantic context (e.g., what 'item_ref' represents), and the description adds nothing.

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 explicitly states the verb 'Create' and the resource 'invoice in QuickBooks Online,' which clearly identifies the tool's primary function. However, it does not differentiate from sibling tools like 'create_sales_receipt' or 'create_credit_memo,' which could lead to confusion for an agent selecting among similar creation tools.

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 alternatives, such as when to create an invoice versus a sales receipt or credit memo. No prerequisites, exclusions, or contextual hints are given, leaving the agent without decision support.

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