awb_create

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

No annotations are provided, so the description carries full burden. It discloses that this is a manual creation, lists parameter fields with types, and provides an example. However, it does not mention auth requirements, error handling, or what happens on duplicate AWB numbers.

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 concise: a single sentence for purpose, then a structured list of parameters with types and descriptions, followed by a clear example. Every sentence adds value with no repetition.

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 tool has an output schema (not shown), so return values are covered. The description provides enough detail to call the tool correctly, including required fields from awb_carrier_list(). Minor gap: does not mention validation or error responses, but for a simple creation tool it is mostly complete.

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 only defines 'data' as a string with no description (0% coverage). The description compensates fully by listing key fields (orderId, carrierId, awbNumber, packages, weight) with types and brief descriptions, plus a concrete example. This adds significant meaning beyond the schema.

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 explicitly states 'Manually create an AWB record for an order', using a specific verb and resource. It distinguishes from siblings like awb_generate (auto-generate) and awb_print (print) by emphasizing manual creation.

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?

The description implies usage context by referencing awb_carrier_list() for the carrierId parameter, but does not explicitly state when to use this tool versus alternatives or provide exclusions. It is clear enough for straightforward creation.

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