Awd_getInboundShipment

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

No annotations are provided, so the description carries the full behavioral burden. 'Retrieves' implies a read-only operation, and 'Runs in your Kuudo deployment, not here' hints at an environment restriction, but the description does not disclose side effects, required permissions, error behavior, authentication needs, or any result/return details.

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, but 'Catalog entry.' is a vague meta statement that does not earn its place, and the actual functional clause is placed at the end. It is compact but not cleanly structured.

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 retrieval tool with no output schema and no annotations, an agent still needs to know what identifies the shipment and what the returned data will look like. The description only gives a terse purpose and a cryptic environment note, leaving too much unspecified for confident 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 has zero properties and schema description coverage is 100%, so there are no parameters the description must explain. The baseline of 4 applies due to the absence of parameters.

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 core statement 'Retrieves an AWD inbound shipment' gives a specific verb and resource, so the main purpose is clear. However, it does not distinguish this from sibling tools like Awd_getInbound or Awd_listInboundShipments, and the opening 'Catalog entry. Runs in your Kuudo deployment, not here.' adds ambiguity.

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 when-to-use or when-not-to-use guidance is provided. The description does not explain when to choose this tool over Awd_getInbound or Awd_listInboundShipments, nor does it mention prerequisites such as having an inbound shipment identifier.

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