fiken_create_invoice_draft

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

The annotations indicate readOnlyHint=false, confirming a write operation. The description aligns by stating 'creates', but adds no additional behavioral context (e.g., idempotency, side effects, or required permissions).

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 (one short sentence), but it omits essential structure such as parameter guidance or usage notes. The brevity undermines clarity for a 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 the tool's complexity (18 parameters, no output schema, many sibling draft tools), the description is severely incomplete. It does not explain the concept of a draft, how it relates to finalizing invoices, or what the response contains.

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?

With 18 parameters and only 22% schema description coverage, the description adds no parameter-level detail. It fails to explain key fields like 'type' (enum of five values), 'lines' structure, or 'daysUntilDueDate' meaning, leaving the agent underinformed.

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 'Creates a new invoice draft' clearly identifies the action (create) and the resource (invoice draft), distinguishing it from sibling tools like fiken_create_invoice (final invoice) and fiken_create_credit_note_draft (credit note draft).

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 usage context is provided; the description does not specify when to use this tool versus alternatives, such as fiken_create_invoice for immediate invoicing or fiken_create_offer_draft for offers. No prerequisites or conditions are mentioned.

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