VendorDirectFulfillmentShippingV1_getShippingLabel

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

With no annotations, the description must carry this weight. It does disclose an important non-obvious behavior — the operation runs in the user's Kuudo deployment, not in the current environment — and says it returns a label. However, it does not state whether the operation is read-only, what failure modes exist, or what the returned label looks like.

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 mostly front-loaded with the important deployment constraint. The 'Catalog entry.' fragment is somewhat redundant with 'not here,' but overall there is minimal waste.

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 simple retrieval with no output schema and an empty input schema, the description names the essential parameter and the outcome. It is not fully complete, though, because it lacks an explicit invocation contract (e.g., parameter location or required flag) and does not distinguish this V1 operation from the 20211228 counterpart.

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 declares zero properties and only allows additionalProperties, so the description's mention of purchaseOrderNumber is the sole semantic information about the key input. It adds real meaning, but stops short of specifying type, requiredness, or how the parameter is passed.

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: it returns a shipping label for a purchaseOrderNumber. It is clear enough to distinguish from submission/confirmation siblings, though it does not explicitly differentiate from the near-identical VendorDirectFulfillmentShipping20211228_getShippingLabel or plural getShippingLabels.

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?

No guidance is given about when to choose this tool over alternatives. The only contextual note, 'Runs in your Kuudo deployment, not here,' hints at a deployment constraint but does not name an alternative or state a selection condition.

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