Create a new invoice in KikoBooks by supplying customer ID, invoice and due dates, and one or more line items with description, quantity, and unit price.
Create a new invoice in KikoBooks. Requires customer ID, dates, and at least one line item with description, quantity, and unit price.
| Name | Required | Description | Default |
|---|---|---|---|
| invoice | Yes |
Changes observed during successful MCP inspections.
v0.2.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a create/mutation but says nothing about permissions, whether the draft is posted or final, idempotency, or what happens to unsupplied defaults — all relevant for a finance write operation.
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?
Two sentences, both front-loaded and free of filler: the action first, then the required inputs. Efficient and easy to scan.
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?
For a mutation tool with nested objects, no annotations, and no output schema, the description is thin — it covers required inputs but leaves behavior, side effects, and handling of the nested lineItems/optional fields unexplained.
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?
Top-level schema description coverage is 0%, so the description must compensate, and it does name the required inputs (customer ID, dates, and line item description/quantity/unit price). However, it omits the many optional fields (memo, termsCode, currencyCode, billing address) that an agent may need to set.
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?
States a specific verb and resource ('Create a new invoice in KikoBooks'), clearly distinguishing it from search/get/update invoice siblings and from create_bill or create_credit_memo. It does not, however, differentiate itself from generate_invoice_from_proposal or generate_invoice_from_job, which are the closest conceptual alternatives.
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 lists required inputs but gives no guidance on when to use this tool versus generate_invoice_from_proposal, generate_invoice_from_job, or generate_recurring_invoice. No prerequisites, ordering, or exclusions are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.