FulfillmentInbound_listTransportationOptions

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

With no annotations, the description carries the behavioral disclosure burden. It usefully indicates a retrieval operation and notes that execution happens elsewhere, but it does not explain what 'Catalog entry' means, whether local invocation is a no-op, or what state must already exist for the shipment.

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 'Catalog entry.' is an unexplained fragment that does not earn its place, and the core action is not front-loaded. 'Runs in your Kuudo deployment, not here' adds context but also introduces ambiguity.

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 list operation in a multi-step fulfillment workflow, the description omits prerequisites, returned data shape, and how the target shipment is identified. The reference to a Kuudo deployment is too cryptic to give the agent confidence about whether and how the tool can actually be invoked.

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 zero properties but allows additionalProperties, so parameter semantics are murky. The description adds only domain context ('for a shipment') and does not identify how the agent should specify the shipment, even though a shipment reference would be expected for this operation.

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 specific verb and resource: 'Retrieves all transportation options for a shipment.' This distinguishes the read operation from sibling generate/confirm transportation-option tools, though it does not name them. The opening phrase 'Catalog entry' is vague and slightly obscures the purpose.

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 about when to call this tool versus FulfillmentInbound_generateTransportationOptions, confirmTransportationOptions, or other list operations. 'Runs in your Kuudo deployment, not here' hints at environment constraints but does not provide selection criteria, prerequisites, or alternatives.

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