ShippingLegacy_createShipment

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

With no annotations, the description carries the full behavioral disclosure burden. It only says the tool runs elsewhere and creates a shipment, without explaining side effects, permissions, required inputs, or what a 'catalog entry' means. The 'not here' note leaves ambiguity about whether direct invocation is even supported.

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, which is generally positive, but the core action is placed last and 'Catalog entry' contributes little. It is adequate but not a model of front-loaded, high-signal writing.

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 mutation-style tool with no annotations and no output schema, this description is incomplete. An agent cannot determine whether the tool is callable, what payload to provide, or what response to expect; the 'not here' statement creates more uncertainty than it resolves.

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?

There are zero declared parameters, so the empty schema requires little explanation and the baseline for 0 params is 4. The description adds no parameter information, but none is strictly needed, though additionalProperties:true remains unaddressed.

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 a specific action and resource: 'Create a new shipment.' However, it does not differentiate this tool from siblings like ShippingLegacy_purchaseShipment or Shipping_purchaseShipment, and the phrase 'Catalog entry' adds ambiguity rather than clarity.

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 alternatives. 'Runs in your Kuudo deployment, not here' hints at an environmental restriction, but it does not explain when to invoke this tool or when to choose a sibling tool instead.

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