invoices_create

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

With no annotations provided, the description fully shoulders behavioral disclosure. It reveals the critical behavior that line_items are ignored by the API, a fact not evident from the schema. This transparency exceeds expectations.

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 with no unnecessary words. The first sentence states the purpose, and the second delivers the essential caveat. Perfectly front-loaded and efficient.

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 creation tool with 11 parameters and no output schema, the description covers the most critical behavioral nuance (line items). However, it does not mention return values or other potential pitfalls, which slightly reduces completeness. Still, the description is largely adequate given the rich schema.

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 schema covers all 11 parameters with descriptions (100% coverage), but the description adds critical meaning by warning that line_items are ignored, which is not reflected in the schema's description of that parameter. This adds significant value beyond the schema.

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 explicitly states 'Create a new invoice' with a clear verb and resource. It distinguishes itself from sibling tools like invoices_add_line_item by noting that line_items are ignored during creation, making the purpose unambiguous.

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?

Provides explicit guidance on when to use this tool (create an invoice) and what not to do (include line_items in the body). It directs users to use invoices_add_line_item after creation, which is an excellent example of when-not-to and alternative tool usage.

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