MerchantFulfillment_createShipment

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

With no annotations, the description carries the full behavioral burden. It only mentions that the tool runs in a Kuudo deployment and creates a shipment; it does not disclose side effects, required data, authorization, or whether this is truly executable here. The phrase 'Catalog entry' adds ambiguity about whether the tool actually performs an action.

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, but it opens with the ambiguous and redundant 'Catalog entry' and deployment note before stating the actual operation. The operative sentence is generic and does not add meaningful structure or actionable detail.

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 mutation-style tool with no output schema and no annotations, the description should explain what information is needed, what side effects occur, and how this relates to the other MerchantFulfillment operations. None of that is present, leaving the definition incomplete for reliable tool selection and invocation.

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 no properties but allows additional properties, so the expected payload is completely unspecified. The description adds no field names, formats, or required shipment details beyond the vague phrase 'with the information provided.' This makes it difficult for an agent to construct a 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 clear action and resource: 'Create a shipment with the information provided.' It is not a tautology and the core purpose is understandable. However, it does not differentiate this tool from the many sibling shipping creation/purchase tools.

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 guidance on when to use this tool versus alternatives such as Shipping_purchaseShipment, ShippingLegacy_createShipment, or MerchantFulfillment_getEligibleShipmentServices. The phrase 'Runs in your Kuudo deployment, not here' hints at environmental constraints but does not clearly state when the tool should or should not be invoked.

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