ShippingLegacy_purchaseLabels

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

With no annotations, the description must carry behavioral disclosure. It does warn that this is a 'Catalog entry' running in the caller's Kuudo deployment, but it does not disclose side effects, permissions, reversibility, or what happens after purchase. For a purchasing operation, this is a notable 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 short, but the first two fragments ('Catalog entry. Runs in your Kuudo deployment, not here.') are cryptic and delay the action statement. It is compact but not optimally clear.

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 operation with no annotations, no output schema, and a crowded sibling space, the description is too thin. It omits how the rate is provided, what the tool returns, whether it is actually invocable, and how it relates to ShippingLegacy_purchaseShipment, Shipping_purchaseShipment, and Shipping_directPurchaseShipment.

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 parameters, so the description should clarify the implicit 'given rate' input. It mentions that a rate drives the purchase but never names the parameter or format, leaving the agent to guess how to supply the rate, especially since additionalProperties is true.

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 core sentence, 'Purchase shipping labels based on a given rate,' states a specific action and object. It is clear what the tool does in isolation, but it does not distinguish itself from sibling tools such as ShippingLegacy_purchaseShipment or Shipping_purchaseShipment.

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 provides no guidance on when to choose this tool over the many purchasing/shipping siblings, nor does it explain the 'Kuudo deployment' context beyond saying it runs 'not here.' There are no explicit use cases, prerequisites, or exclusions.

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