DeliveryByAmazon_submitInvoice

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It indicates that the operation runs outside the current environment and implies a write action, but it does not explain side effects, prerequisites, authentication needs, or what happens after submission. The 'not here' note is a useful behavioral trait, but the operational behavior remains largely undisclosed.

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 free of filler, with each clause contributing either deployment context or the core operation. The three fragments feel slightly abrupt, but the content is efficient and front-loads the most important environmental 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 tool with no annotations, no output schema, and no defined parameters, the description leaves significant gaps. It does not specify what inputs are required, what the response looks like, or how this relates to the sibling ShipmentInvoicing_submitInvoice. As a catalog entry, the 'not here' statement is helpful, but it is not enough for an agent to correctly invoke or reason about the tool.

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 contains zero defined parameters, so the baseline is 4. The description adds the only semantic clue: the invoice is tied to 'a given order or shipment,' implying an identifier or reference is needed. It does not name concrete parameters, but with no schema properties to document, the description provides reasonable minimal context.

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 action and resource: 'Submits a shipment invoice for a given order or shipment.' This goes beyond the tool name by specifying the invoice type and target. However, it does not differentiate from the very similar sibling ShipmentInvoicing_submitInvoice, and the 'Catalog entry' opener adds context rather than clarifying purpose.

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 a useful environmental constraint: 'Runs in your Kuudo deployment, not here.' This tells the agent not to treat the tool as locally invocable. However, it gives no explicit guidance about when to use this tool versus related alternatives such as ShipmentInvoicing_submitInvoice or DeliveryByAmazon_getInvoiceStatus.

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