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

Annotations already indicate non-read-only, non-destructive, and non-idempotent behavior. The description adds valuable context: it reveals the output is a base64-encoded PDF returned in "PickupDocument." It also clarifies the tool creates a manifest (a side effect), aligning with the create semantics. No contradiction with annotations.

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 two sentences (plus a [DEMO] marker), front-loads the core purpose, and every clause provides useful information. It avoids redundancy and is appropriately sized for the tool's complexity.

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 output schema, annotations, and full parameter descriptions, the description is largely sufficient. It covers the essential purpose and return format. It lacks explicit usage context (e.g., when a manifest is needed, how to obtain PickupDocument) but this is not critical given the structured data. Overall, the description is complete for a straightforward creation tool.

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?

Schema description coverage is 100%: all four parameters (TxnIds, Force, Provider, AirwayBillId) have descriptions in the schema. The tool description does not add parameter-level information, so baseline 3 is appropriate since the schema fully handles parameter semantics.

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 uses the specific verb "Create" with a clear resource "carrier manifest / SCAN form" and scope "for a list of orders." This directly distinguishes it from sibling tools like teapplix_purchase_label or teapplix_get_orders by describing a distinct operation.

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 phrase "for a list of orders" implies the tool should be used when generating a manifest from order IDs, but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. No alternative tools are named, giving only implied context.

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