FulfillmentInboundV0_getShipments

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

With no annotations, the description carries the transparency burden. It does disclose the key behavioral trait that the tool runs externally, not in the current environment, and that it is a read-style operation returning a list. It does not disclose return shape, pagination, or required permissions, but for a simple list operation the main caveat is stated.

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 front-loaded with the important deployment caveat before the function statement. The only weak element is the jargon phrase 'Catalog entry,' but there is no redundant filler.

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 that there are no annotations and no output schema, the description must supply the return shape, the criteria, and enough context to choose among many siblings. It provides neither the criteria names nor any output detail, so an agent cannot fully determine how to invoke or interpret the result.

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 zero declared parameters, so the baseline is generous, but the text claims criteria can be specified without naming any of them. 'Criteria that you specify' adds the idea of filtering, yet the agent is left to guess which criteria are accepted, especially because additionalProperties is true.

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 verb and resource: it 'Returns a list of inbound shipments based on criteria that you specify.' This is not a tautology, but it does not differentiate from closely related siblings such as FulfillmentInbound_getShipment or Awd_listInboundShipments.

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?

It gives an important execution context ('Runs in your Kuudo deployment, not here') that tells the agent this tool is not for the current environment, and 'criteria that you specify' implies a filtering use case. However, it names no alternative tools and gives no concrete conditions for choosing this over the many shipment-related siblings.

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