Awd_getInbound

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

Annotations are absent, so the description carries the full burden for behavioral disclosure. It only says it 'retrieves' an order and 'runs in your Kuudo deployment, not here,' which is vague and potentially contradictory. There is no mention of read-only behavior, required context, errors, authentication, or what happens when this runs in a different deployment.

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 and mostly efficient, but 'Catalog entry' is low-value noise and the order of clauses is awkward: the misleading catalog framing precedes the actual purpose. 'Runs in your Kuudo deployment, not here' may be important context but is not clearly explained.

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 tool with no output schema and no annotations, the description is inadequate for an agent to confidently invoke it. It does not state what identifies the inbound order, what the return value looks like, or whether the tool is actually callable given the claim that it runs 'not here.' The catalog-entry framing adds ambiguity rather than resolving it.

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?

With zero parameters in the schema and 100% schema coverage, the baseline is 4. The description offers no parameter detail, but none is required for a tool whose schema declares no properties. The schema's additionalProperties:true leaves room for unexpected inputs, but the description does not need to compensate for missing param documentation.

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 clear action and resource: 'Retrieves an AWD inbound order.' This distinguishes it from the sibling Awd_getInboundShipment, which targets a shipment rather than an order. However, the opening 'Catalog entry' is confusing and slightly undermines what the tool actually does.

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 when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives or explain why an agent should choose this over Awd_listInboundShipments or Awd_getInboundShipment. The phrase 'Runs in your Kuudo deployment, not here' hints at an environment restriction but does not clarify how that should affect invocation.

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