freshbooks_create_invoice

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by stating that created invoices start as drafts, that confirm:true is required to execute, and that omitting it produces a dry-run preview with no network call. It stops short of describing the preview's content or whether execution is idempotent.

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?

Three short sentences, each carrying essential information: the action, the lifecycle outcome, and the safety/confirmation behavior. It is front-loaded and contains no filler.

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 an 8-parameter tool with nested objects and no output schema, the description captures the critical safety behavior but omits what the successful response or preview contains. The agent can still operate because confirm:false provides a safe preview, but return-value expectations are left implicit.

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 88%, so the parameters are already well documented. The tool description does not add meaning beyond the schema; it restates the confirm behavior that the schema already describes. This meets the baseline but does not exceed it.

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 verb ('Create'), the resource ('an invoice'), and the target ('for a client'). It is unambiguous and distinct from sibling tools like freshbooks_update_invoice or freshbooks_create_client.

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 implies when the tool should be used ('Create an invoice') and explains the confirmation requirement, but it does not explicitly contrast this with alternatives such as freshbooks_update_invoice or mention when not to use it. Usage is mostly inferred from the tool name and first sentence.

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