FulfillmentOutbound_getFulfillmentPreview

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

With no annotations, the description carries the transparency burden. It does disclose a significant behavioral caveat: this is a catalog entry that runs in the user's Kuudo deployment, not in the current environment. It also implies a read-only list operation, but it omits details about authorization, side effects, rate limits, or error behavior.

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 three short, non-redundant sentences. The execution-location caveat is front-loaded, and the functional sentence is clear. No words are wasted.

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 tool with an empty schema, no output schema, no annotations, and vague 'shipping criteria,' the description is not sufficient for an agent to invoke it correctly. The agent would not know which criteria are valid, how they should be structured, or what the response shape is. The deployment warning is useful but does not fill those gaps.

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 schema declares zero properties but allows additionalProperties, so the description's mention of 'shipping criteria that you specify' is the only meaningful parameter guidance. The baseline for a zero-parameter schema is 4, and the description adds a useful hint even though it does not enumerate valid criteria.

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 clear purpose: it returns a list of fulfillment order previews based on shipping criteria. This distinguishes it from order-mutation siblings like createFulfillmentOrder and cancelFulfillmentOrder, though it does not explicitly name an alternative.

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 related shipping or fulfillment tools. The phrase 'based on shipping criteria that you specify' is only an implicit usage hint, with no exclusions, prerequisites, or alternative tool references.

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