teamleader_invoice_draft

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

No annotations are supplied, so the description bears full responsibility for behavioral disclosure. It only says 'create', implying a mutation operation, but does not detail permissions, side effects, reversibility, or what happens upon creation. This transparency gap is significant for a tool with no annotations.

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, focused sentence with no wasted words. It is front-loaded and appropriately sized for the tool's straightforward action, earning full marks for conciseness.

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?

The tool has 7 parameters, 5 required, no annotations, and no output schema. The one-sentence description does nothing to explain the context of creating a draft invoice, such as the meaning of grouped_lines, payment term types, or the relationship with customers and departments. This is severely incomplete for such a complex tool.

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 input schema provides descriptions for 86% of parameters (6 out of 7), so the schema carries most of the semantic load. The description adds no parameter-specific information, which aligns with the baseline for high schema coverage.

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 'Create a new draft invoice in Teamleader Focus', using a specific verb and resource. It distinguishes itself from sibling tools like teamleader_invoice_send, teamleader_invoice_book, and teamleader_invoice_delete by focusing specifically on draft creation.

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites, such as needing an existing customer or department, nor does it reference related tools like quotations or other invoice actions.

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