VendorDirectFulfillmentShippingV1_getPackingSlips

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

With no annotations provided, the description carries the behavioral burden. It discloses that this is a catalog entry and that it runs elsewhere ('not here'), which is important context. It also indicates a read-style operation by saying 'Returns a list,' but it does not mention pagination, criteria specifics, or any other execution 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 short and efficient, with no filler. The 'Catalog entry' sentence adds a little redundancy with 'Runs in your Kuudo deployment, not here,' but overall the content is compact and readable.

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 no parameters and no output schema, the description provides the essential action and environment context. However, it leaves 'criteria specified' undefined and does not describe what a packing slip response would contain, which matters because no output schema is available to fill that gap.

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 has zero parameters, so the baseline is 4; the description does not need to document individual parameters. The phrase 'criteria specified' is somewhat vague and unsupported by the empty schema, but it does not directly contradict the schema.

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 action ('Returns a list of packing slips') and identifies the resource ('purchase orders that match the criteria specified'). The plural 'packing slips' and 'list' help distinguish it from the singular getPackingSlip sibling, though it does not explicitly name that 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?

The description gives a clear contextual signal: 'Runs in your Kuudo deployment, not here,' which tells the agent this tool is not executable in the current environment. However, it does not explicitly say when to prefer this over the many related sibling tools, such as getPackingSlip or the 20211228 variant.

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