ShippingLegacy_purchaseShipment

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

No annotations are provided, so the description carries the full burden. It only says 'Purchase shipping labels' and 'Runs in your Kuudo deployment, not here.' It does not disclose side effects, costs, rate limits, required setup, idempotency, or the meaning of 'Catalog entry'. For a purchasing operation, the lack of behavioral disclosure is a significant gap.

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 extremely short, which is concise, but it is under-specified rather than efficiently structured. 'Catalog entry' is confusing filler, and the front-loaded location note wastes the first sentence on something that does not help select or invoke the tool. The meaningful action 'Purchase shipping labels' is present but no supporting structure exists.

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?

This is a purchasing tool with no output schema, no annotations, no parameter documentation, and no guidance among many similar siblings. The description is far too thin: it does not state what inputs are needed, what the response contains, how this differs from Shipping_purchaseShipment or ShippingLegacy_purchaseLabels, or what 'Runs in your Kuudo deployment' means operationally.

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 is an empty object with additionalProperties true, so there are zero defined parameters. With 0 parameters, the baseline is 4 and the description does not need to explain parameters. However, additionalProperties true means callers might pass arbitrary properties, and the description gives no hint about what those could be.

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 says 'Catalog entry. Runs in your Kuudo deployment, not here. Purchase shipping labels.' It does state the action 'purchase shipping labels' but the 'Catalog entry' phrasing is vague and it doesn't differentiate from the many related shipping purchase siblings like Shipping_purchaseShipment, Shipping_directPurchaseShipment, or ShippingLegacy_purchaseLabels. The tool name already implies purchasing a shipment, so the description adds little beyond a tautology.

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 the numerous sibling tools such as Shipping_purchaseShipment, Shipping_directPurchaseShipment, ShippingLegacy_purchaseLabels, etc. The only usage note is 'Runs in your Kuudo deployment, not here', which is a location constraint but not a usage guideline. The description does not explain prerequisites, when not to use it, or which alternative to choose.

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