ShipmentInvoicing_submitInvoice

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the operation submits an invoice and runs in a remote Kuudo deployment, but it does not disclose side effects, idempotency, validation behavior, duplicate handling, required authorization, or what happens on success or failure. For a mutating tool, this is a significant transparency 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 short and mostly free of fluff, but the first two sentences, 'Catalog entry' and 'Runs in your Kuudo deployment, not here,' are secondary context that precedes the actual purpose statement. It would be more effective to front-load 'Submits a shipment invoice document for a given shipment' and then add the environment caveat.

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 mutating tool with no annotations, no output schema, no defined parameters, and no sibling differentiation, the description is materially incomplete. An agent knows the high-level action but lacks the shipment identifier specification, expected request format, response details, and any behavioral caveats needed to invoke the tool correctly.

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 is empty with additionalProperties true, so the description's phrase 'for a given shipment' is the only hint that a shipment identifier is relevant. Because there are zero defined parameters, the baseline is 4, but the description fails to name the expected property or its format, leaving the agent to guess how to specify the shipment. The hint adds some meaning beyond the empty schema but is not sufficient for correct invocation.

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 specific action and resource: 'Submits a shipment invoice document for a given shipment.' This clearly communicates the tool's purpose and is not a mere restatement of the name. It does not explicitly differentiate from similar siblings like DeliveryByAmazon_submitInvoice or Messaging_sendInvoice, but the ShipmentInvoicing namespace plus 'shipment invoice document' provides adequate differentiation.

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 provides only an environment note ('Runs in your Kuudo deployment, not here') and no guidance on when to use this tool versus siblings such as ShipmentInvoicing_getShipmentDetails, ShipmentInvoicing_getInvoiceStatus, or DeliveryByAmazon_submitInvoice. There are no prerequisites, exclusions, or condition-based routing instructions, so an agent cannot decide when this tool is the correct choice.

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