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 and does so excellently. It discloses that invoices start as drafts, requires confirm: true, and that omitting it makes no network call—critical behavioral information for a mutation tool.

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, zero filler. Front-loaded purpose followed by the essential execution requirement. Every word earns its place.

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 8 parameters, nested objects, and absence of output schema, the description captures the critical workflow (draft status, confirm gate, dry-run) comprehensively. It could specify the return format more explicitly, but the schema-rich context makes the description adequate.

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 coverage is high (88%) with detailed descriptions for all significant parameters. The description reinforces confirm semantics but adds minimal extra meaning beyond the schema. The schema already documents the dry-run behavior, so the description's contribution to parameter understanding is limited.

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 'Create an invoice for a client' with a specific verb and resource. This distinguishes it from siblings like get_invoice, list_invoices, and update_invoice, leaving no ambiguity about the tool's purpose.

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?

It provides key context that confirm: true is required to execute and that without it the tool returns a dry-run preview. However, it does not explicitly compare against alternatives such as freshbooks_update_invoice for modifying existing invoices, so usage guidance is implied rather than fully differentiated.

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