VendorDirectFulfillmentShipping20211228_getPackingSlip

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the run location and return value, but it does not disclose whether the operation is read-only, what authentication or environment requirements exist, what the response looks like, or how errors behave. The 'not here' statement is too vague to be actionable.

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 appropriately brief and gets to the action quickly. The 'Catalog entry' phrase is somewhat unclear and adds limited value, but the overall structure is compact and front-loads the main behavior.

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?

The tool has no output schema, no annotations, and an empty input schema, so the description must supply more context. It mentions purchaseOrderNumber but does not explain how to pass it, what the returned packing slip looks like, or what 'Runs in your Kuudo deployment, not here' means for actually invoking the tool. This is not enough for confident selection and correct invocation.

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 is empty, so the description adds meaningful value by explicitly naming purchaseOrderNumber as the input. However, it does not specify the parameter type, required status, or how the parameter is passed, so it is not a complete parameter description. With zero parameters in the schema, the baseline is 4, and the description earns that by at least identifying the key input.

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 action and resource: 'Returns a packing slip based on the purchaseOrderNumber that you specify.' This is clear enough for an agent to understand the core function, though it does not explicitly differentiate itself from sibling tools like getPackingSlips or the V1 counterpart, so it falls short of a 5.

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 provides no guidance on when to use this tool versus the many sibling tools. The clause 'Runs in your Kuudo deployment, not here' hints at an environment constraint but does not explain when an agent should select this tool over alternatives.

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