alonomic_create_parcel

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

Since no annotations are provided, the description carries full burden. It warns of billing and explains the error response when ordering is disabled. It does not mention side effects like irreversibility, but the warning about 'real business parcel' implies a permanent mutation. Overall transparent enough.

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 well-organized with a bold warning, Persian text, endpoint mapping, and structured Args. It is informative but slightly verbose; could be more concise without losing clarity.

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 complex tool with 6 parameters, nested objects, and no schema descriptions, the description is comprehensive. It covers all necessary information: purpose, preconditions, error handling, parameter structures, and endpoint. The presence of an output schema further reduces burden.

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 coverage is 0%, so the description fully explains each parameter. The Args section provides detailed structure for drop, parcel, pickup, delivery_proofs, parcel_extra_params, and instance, including nested objects and optional fields. This exceeds what the schema alone offers.

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 the verb ('Create') and resource ('REAL business parcel'), and includes a warning about billing. It distinguishes from siblings such as alonomic_calc_parcel (calculation vs. creation) and alonomic_update_parcel (update vs. create).

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 specifies prerequisites: Alonomic credentials, enable_ordering=true, read_only=false. It also warns about billable nature. Although it doesn't explicitly state when not to use it, the precondition effectively guides usage. Could mention alternatives like alonomic_calc_parcel for non-billable estimates.

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