FulfillmentInboundV0_getPrepInstructions

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

With no annotations, the description must carry the behavioral burden. It discloses that the tool is a catalog entry, runs elsewhere, and returns instructions rather than mutating state. It does not mention permissions, rate limits, or required inputs, but for a non-runnable catalog entry this is a reasonable minimum.

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?

Three short sentences, with the most important routing information ('Catalog entry... not here') front-loaded. No filler or redundant restatement of the tool name.

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 zero declared parameters and no output schema, the description tells an agent what the operation returns and that it is not available in this environment. It lacks detail on the shape of the returned instructions, but for a catalog-entry stub this is close to complete.

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 and 100% coverage, so there are no parameter details for the description to add. The description offers no parameter-level detail, but none is required in this schema; the additionalProperties:true caveat is not addressed.

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?

States a clear retrieval verb ('Returns') and a specific resource ('labeling requirements and item preparation instructions'), which distinguishes it from the many other FulfillmentInbound commands in the sibling list. The odd 'Catalog entry' phrasing is immediately clarified by the rest of the description.

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?

Provides an explicit execution-context constraint: the tool runs in the user's Kuudo deployment, not here, so an agent knows not to invoke it in the current environment. However, it gives no guidance on when to choose this over related prep-related siblings such as listPrepDetails or setPrepDetails.

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