VendorDirectFulfillmentShippingV1_getShippingLabels

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

With no annotations provided, the description carries the full burden. It adds useful behavioral context by noting the tool is a catalog entry and runs in the user's Kuudo deployment, and it indicates a read-style 'returns a list' operation. However, it does not disclose pagination, response shape, or potential side effects, leaving some behavior implicit.

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 front-loads the key operational detail about returning shipping labels. The opening 'Catalog entry' and 'not here' phrasing is cryptic and slightly distracting, but the overall structure is compact and economical.

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 output schema, no annotations, and an empty input schema, the description is too thin. It fails to clarify how the time frame should be specified, what fields a shipping label includes, or how this tool relates to sibling label and fulfillment tools. The 'not here' note raises more questions than it answers.

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 has zero parameters, so the baseline is 4, but the description mentions a 'time frame that you specify' without corresponding schema properties. This adds semantic meaning beyond the schema but does not tell the agent how to encode the time frame, making the parameter behavior ambiguous despite additionalProperties being true.

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 clearly states the operation: it returns a list of shipping labels filtered by a time frame. The phrase 'list of shipping labels' distinguishes it from singular label retrieval tools, but it does not explicitly differentiate among the multiple getShippingLabels sibling versions.

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?

No explicit guidance is given about when to use this tool instead of the many sibling tools, such as submitShipmentConfirmations or getPackingSlips. The note 'Runs in your Kuudo deployment, not here' provides environment context but not decision guidance.

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