VendorShipmentsV1_GetShipmentLabels

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

With no annotations, the description carries the full behavioral burden. It meaningfully discloses that this is a 'Catalog entry' and that it 'Runs in your Kuudo deployment, not here,' which is crucial context preventing an agent from expecting local execution. However, it omits side-effect status, required permissions, error behavior, and what happens when no filters are supplied.

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 caveats front-loaded before the behavior statement. 'Catalog entry' is jargon that could be clearer, but otherwise every word earns its place and the description is efficiently sized.

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?

With an empty input schema, no annotations, and no output schema, the description must carry significant weight. It communicates the return type and that filters drive the call, but not which filters are valid or the label output format. The 'not here' disclosure reduces the practical need for full invocation details, but as a callable tool definition it remains incomplete.

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 with additionalProperties: true, so the description is the only source of parameter meaning. It adds that the tool is filter-driven ('based on the filters that you specify') but never enumerates the valid filters, their names, types, or formats, leaving an agent unable to construct a proper call.

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 small parcel shipment labels based on the filters that you specify.' The 'small parcel' qualifier helps separate this from the sibling direct-fulfillment getShippingLabels tools. The opening 'Catalog entry' phrase is confusing and slightly obscures the actual function, 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?

No guidance is provided on when to use this tool versus the sibling VendorDirectFulfillmentShipping*_getShippingLabels or VendorShipmentsV1_GetShipmentDetails tools. The only contextual hint, 'Runs in your Kuudo deployment, not here,' warns about the execution environment but does not help an agent choose among the many similar label/document tools or state when not to use it.

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