Create a courier parcel (book a delivery)

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

Annotations indicate non-readonly and non-destructive; description adds that it creates a booking, uses invoice as idempotency key, and returns consignment/tracking. No contradiction, but does not mention rate limits or error handling.

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 concise sentences, front-loaded with purpose, followed by essential details. No redundant information.

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 9 parameters and nested meta object, description addresses key nuances (idempotency, COD unit, Pathao ID resolution). Lacks mention of duplicate invoice handling and error scenarios, but overall sufficient for selection and invocation.

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 covers 44% of params with descriptions; description adds meaning to codAmount (BDT, 0=prepaid), invoice (unique per order), and meta (Pathao structure with ID resolution). Other params like recipientName and address lack extra context but schema provides types.

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?

Clearly states booking a delivery with Bangladesh courier, returns consignment id and tracking code. Distinguishes from siblings like list_couriers or track_parcel.

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?

Provides guidance on COD amount unit, invoice uniqueness for idempotency, and need to resolve IDs via get_courier_locations for Pathao. Could explicitly state when not to use or alternatives, but context from sibling tools helps.

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