awb_generate

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

With no annotations, the description only states it generates an AWB automatically, but does not disclose side effects, permissions, idempotency, or state changes.

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 concise with a clear header and structured parameters section, including an example. No wasted words, and front-loaded with the purpose.

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?

Given the existence of an output schema, the description does not need to explain return values. It covers input structure well but lacks info on error handling or prerequisites.

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 has 0% coverage for the single string parameter 'data', but the description compensates by detailing the expected JSON structure with key fields and an example, adding significant 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?

The description clearly states 'Generate an AWB automatically through the carrier's integrated API,' using a specific verb and resource. It distinguishes from sibling 'awb_create' by implying automated integration.

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 provides an example and references 'awb_carrier_list()' for carrierId, but does not explicitly state when to use this tool versus alternatives like 'awb_create' or when not to use it.

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