Shipping_getUnmanifestedShipments

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

With no annotations, the description carries the full behavioral burden. It discloses a key operational trait ('Runs in your Kuudo deployment, not here') and implies a read-only 'Get' operation, but it does not describe side effects, required permissions, invocation results, or what happens if called in this environment.

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 and each sentence adds information: catalog status, deployment scope, and the operation. It is not bloated, though grammar issues such as 'This API Get' and the ambiguous 'unmanifested carriers' phrasing reduce polish.

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?

Given no output schema and no annotations, the description is the sole source of context, but it leaves critical ambiguity around the resource ('carriers' vs 'shipments'), what 'with shipment locations' means, and what the tool returns. The deployment warning is helpful, but the core operation is not sufficiently specified for reliable selection or invocation.

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 empty, so there are no parameters whose semantics need explaining. With 0 parameters, the baseline is 4, and the description does not need to compensate for any undocumented fields.

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 verb and resource ('Get all unmanifested carriers with shipment locations'), but it does not clearly align with the tool name 'getUnmanifestedShipments'—'carriers' vs 'shipments' is a material mismatch. The prefatory labels 'Catalog entry' and 'Runs in your Kuudo deployment' further muddy what the operation actually does for the agent.

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 line 'Runs in your Kuudo deployment, not here' provides an explicit when-not-to-use signal for the current environment, which is useful. However, it gives no guidance on when to prefer this tool over any Shipping_* sibling or what conditions warrant calling it.

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