VendorDirectFulfillmentShipping20211228_getShippingLabel

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

With no annotations, the description carries the behavioral burden. It usefully discloses that this is a catalog entry that runs in a Kuudo deployment rather than here, and implies a read-only label retrieval. However, it does not mention output format, authentication, error behavior, or whether the operation is safe to call directly.

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 only two sentences and gets to the main function quickly. The opening 'Catalog entry' is somewhat cryptic, but the overall text is tightly written with 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 an agent deciding whether and how to invoke this tool, the description is incomplete. It explains that the tool does not run here but does not say what the agent should do instead, how to pass the purchaseOrderNumber, or what the returned label looks like. The missing guidance is especially problematic given the large sibling set.

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 description mentions a purchaseOrderNumber that the user would specify, but the input schema has zero properties. This is a meaningful contradiction: the agent is told a parameter exists but is given no schema slot or format for it. The description adds identification of the key value, but not enough to invoke the tool reliably.

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 clearly states the tool returns a shipping label for a specified purchaseOrderNumber, which identifies the verb and resource. It does not explicitly differentiate from the very similar V1_getShippingLabel or the plural getShippingLabels, so it falls just short of full distinction.

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 says the tool 'runs in your Kuudo deployment, not here,' which is a deployment constraint, but it gives no guidance on when to use this tool versus the many sibling shipping-label tools. It does not name alternatives or explain whether this tool should ever be invoked from the current environment.

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