invoices_create_invoice

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

Annotations indicate readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, but the description adds no behavioral context beyond these. It does not mention that creation implies non-idempotency, potential side effects (e.g., generating invoice numbers, sending emails), prerequisites like business details or payment methods, or what happens on success. With no extra explanation, the description fails to inform the agent of any important behaviors.

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 at two words, which is efficient, but it lacks any structure or front-loading of important information. It essentially restates the tool name without providing additional insight. While conciseness is good, it is under-specified rather than appropriately concise for a 23-parameter 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 (23 parameters, 9 required, nested objects), the description is severely inadequate. It does not explain the purpose beyond creation, required fields, expected outcomes, or any caveats. The annotations and schema provide some structure, but the description fails to tie them together or provide any operational context. For a create operation this complex, the description is critically incomplete.

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 83%, so most parameters already have descriptions in the input schema. The tool description itself adds no additional parameter semantics, but since the schema does the heavy lifting, a baseline of 3 is appropriate. The description does not clarify relationships or usage of complex nested objects beyond what the schema provides.

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 states a clear verb and resource: 'Create Invoice'. It matches the tool name 'invoices_create_invoice' and is not a tautology, but it is minimal and does not differentiate from sibling tools like 'invoices_create_invoice_from_estimate' or 'invoices_create_invoice_template'. The purpose is understandable but lacks any distinguishing context.

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?

There is no guidance on when to use this tool versus the many invoice-related siblings (e.g., invoicing from estimate, creating templates, scheduling). The description gives no context about the appropriate use case, alternatives, or exclusions. This is a significant gap given the large sibling list.

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