business_create_invoice

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

No annotations are provided, and the description does not state whether actual side effects occur or whether the preview_only parameter prevents persistence. It also does not disclose output behavior, error scenarios, or required authentication. Since the description carries the full burden here, this is a notable gap.

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 concise sentence with no filler. The phrase 'under one exact Project ref' is slightly awkward, and 'create or stage' could be more precise, but overall it is compact and to the point.

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 description lacks prerequisites, side effects, return-value expectations, and relationship to related invoice tools. With 11 optional parameters, it is unclear which fields are actually needed for meaningful use, and the output schema is not described.

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 has 0% description coverage and the description adds no parameter-level meaning. Fields such as line_items (typed as string with default '[]'), provider, reference, and preview_only are ambiguous without further explanation.

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 identifies creating or staging an invoice preview scoped to one exact Project ref, which distinguishes it from generic invoice creation by emphasizing project scope. It does not explicitly name sibling alternatives, but the core purpose is understandable.

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 explicit when-to-use or when-not-to-use guidance, and sibling tools such as xero_create_invoice, stripe_create_invoice, or propose_contract_to_cash_invoice are not referenced. The project-ref scope is the only implicit differentiator, so an agent receives limited guidance on choosing this tool over alternatives.

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