FulfillmentInbound_updateShipmentSourceAddress

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

No annotations are provided, so the description carries the full behavioral burden. It reveals that the operation mutates a shipment's source address, but it does not disclose permissions, side effects, reversibility, validation rules, or response behavior. The environment note is not a substitute for behavioral transparency.

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 core functional sentence is concise and clear. However, 'Catalog entry' and 'Runs in your Kuudo deployment, not here' are additional fragments that do not earn their place and may distract from the tool's purpose.

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 operation with no annotations and no output schema, the description should clarify how the existing shipment is identified and what constraints apply. It does neither, and the cryptic environment note raises more questions than it answers.

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 has zero documented properties and no required parameters, so there is little for the description to add. The baseline for zero-parameter tools is 4, and the description neither helps nor hurts parameter understanding.

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 operation: 'Updates the source address of an existing shipment.' This clearly identifies the resource and action. However, it does not explicitly contrast with sibling update tools like FulfillmentInbound_updateShipmentName or updateShipmentTrackingDetails, and the 'Catalog entry' prefix adds ambiguity.

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, no prerequisites, and no mention of shipment state constraints. The note 'Runs in your Kuudo deployment, not here' may confuse an agent about whether the tool is actually invocable in this context.

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