Awd_listInboundShipments

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

With no annotations, the description carries the behavioral burden. It does disclose that this is a catalog entry that runs in the Kuudo deployment rather than here, and 'Retrieves' implies read-only, but it omits output shape, pagination, and filter semantics.

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 minimal waste, and the core action is stated once. 'Catalog entry' and the deployment note are somewhat redundant but do not bloat the description.

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 incomplete for a tool with no output schema and no annotations: it does not describe the returned summary fields, pagination, or how filters are expressed. The environmental note is useful, but the invocation contract remains under-specified.

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 defines no parameters, yet the description mentions optional filters without naming or typing them. This adds a hint beyond the empty schema but leaves the agent without enough information to construct a filtered 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 names the verb 'Retrieves' and the resource 'inbound AWD shipments', with a merchant scope and optional filters. It clearly conveys a list/summary operation, though it does not explicitly contrast with sibling Awd_getInboundShipment.

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 choose this tool over alternatives such as Awd_getInboundShipment or FulfillmentInbound list operations. The 'Runs in your Kuudo deployment, not here' note gives deployment context but not selection criteria.

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