Awd_getInboundShipmentLabels

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal an important trait: the tool runs in the Kuudo deployment, not in the current environment. It also implies a read-only retrieval operation, but it does not disclose output format, error behavior, authorization needs, or what exactly 'box labels' returns.

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 very short and free of unnecessary detail. 'Catalog entry' and 'Runs in your Kuudo deployment, not here' add caveat context, while the core retrieval purpose is clearly present. It could be slightly better front-loaded by leading with the action, but overall it is efficient.

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 description is not sufficient for an agent to confidently call this tool. It does not specify how to pass the shipment ID, what the label output looks like, or whether the tool is even invocable from the current environment given the 'not here' caveat. The empty schema and absent output schema make these gaps material.

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 properties but allows additionalProperties, so the description is the only source of parameter intent. It identifies the key concept ('shipment ID that you specify') even though it fails to give the actual property name or format. With 0 declared parameters, the baseline is 4, and the description adds some semantic meaning.

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?

Description states a specific action ('Retrieves the box labels') and a specific resource ('for a shipment ID that you specify'). This is clear enough to distinguish from the sibling Awd_getInboundShipment, which suggests full shipment data rather than labels, though it never explicitly differentiates itself.

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 about when to choose this tool over alternatives like Awd_getInboundShipment or Shipping_getShipmentDocuments. The odd phrase 'Runs in your Kuudo deployment, not here' hints at an environment limitation but does not tell the agent when to use or avoid the tool.

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