Invoices_createGovernmentInvoice

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose two meaningful traits: the operation is asynchronous and it runs in the Kuudo deployment rather than locally. However, it omits what the submission response contains, whether the operation is idempotent, failure modes, or any side effects, leaving the agent without a full behavioral picture.

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 very short and avoids fluff, with the valuable qualifiers 'Runs in your Kuudo deployment' and 'asynchronous' present. The standalone 'Catalog entry' fragment is redundant and adds little meaning, and the main verb is placed last, slightly reducing front-loading, but overall the text is appropriately compact.

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 tool is a create/submit operation with no annotations, no output schema, and an open-ended input schema (additionalProperties: true). The description does not explain what payload is expected, how to confirm the async request was accepted, or how to retrieve the resulting government invoice (e.g., via a status sibling). The remote-deployment note is helpful but does not make the tool safely invocable.

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 declares zero properties, so the schema covers 100% of declared parameters and the description need not explain them. The baseline of 4 applies here. The description adds no parameter detail, but with no documented parameters that is acceptable, despite the additionalProperties: true flag leaving the request body unexplained.

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 uses a specific verb ('Submits') and resource ('government invoice creation request'), and adds the important qualifier 'asynchronous' so the agent understands the tool only triggers a request rather than returning a completed invoice. It does not explicitly contrast with sibling tools like Invoices_getGovernmentInvoiceStatus or Invoices_createInvoicesExport, but the name and wording make the core purpose clear.

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 guidance on when to use this tool versus alternatives such as Invoices_createInvoicesExport, DeliveryByAmazon_submitInvoice, or ShipmentInvoicing_submitInvoice. The phrase 'Runs in your Kuudo deployment, not here' gives execution-context information but does not explain selection criteria, prerequisites, or when not to use the tool.

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