VendorShipmentsV1_GetShipmentDetails

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, but it only says the tool 'Returns' details and runs in a deployment. It does not clarify whether this is a read-only operation, what 'Runs in your Kuundo deployment, not here' means operationally, or whether pagination, limits, or authentication caveats apply.

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, but it starts with the unhelpful fragment 'Catalog entry.' and the deployment note before reaching the actual functionality. The sentence listing returned data is useful, yet the structure is not optimally front-loaded and contains vague filler.

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 no annotations, no output schema, no documented parameters, and a large sibling tool set, the description is incomplete. An agent cannot determine the response shape, the required filter syntax, or the practical difference between this tool and other shipment-detail tools, so it lacks enough context to invoke it confidently.

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, and the description mentions 'filter parameters value' without naming or describing any parameters. This adds some meaning beyond the schema by suggesting that arbitrary filters can be supplied, but it is too vague for an agent to know what valid filter values look like.

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 names a specific verb ('Returns') and resource ('Details about Shipment, Carrier Details, status of the shipment, container details'), so an agent can generally tell what the tool does. However, the opening 'Catalog entry' and 'Runs in your Kuundo deployment, not here' add confusion and do not help distinguish it from the many sibling shipment tools.

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?

There is no guidance on when to use this tool versus alternatives like VendorShipmentsV1_GetShipmentLabels or VendorDirectFulfillmentShippingV1_getShippingLabels. The phrase 'based on the filter parameters value' hints at query filters but gives no conditions, prerequisites, or exclusions, leaving the agent without a basis for selection.

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