create_invoice

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

With no annotations, the description adds some behavioral context: monetary values must be strings to avoid floating-point issues. However, it does not disclose other critical behaviors (e.g., required fields, side effects, authorization needs).

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 three clear, purposeful sentences with no redundancy. It front-loads the core action, then provides a data type tip and a prerequisite instruction efficiently.

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 complexity of a create tool (likely many parameters, side effects, and no output schema), the description is too brief. It lacks details on required fields, return values, error states, and other critical context.

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 input schema has 0 parameters, so the description carries the full burden. It implies parameters for monetary values and IDs from list_taxes/list_document_types, adding meaning beyond the schema. But it does not explicitly list all expected parameters.

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 tool's action: 'Create a new sales invoice.' It uses a specific verb and resource, and is distinct from sibling tools like create_bill and create_credit_note.

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 advises using list_taxes and list_document_types to obtain valid IDs before calling, which provides clear prerequisite context. However, it does not explicitly state when not to use this tool or compare with siblings.

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