Create draft parcel order

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

Description adds 'Does not purchase a label' and 'update an existing draft' beyond annotations. No contradiction with readOnlyHint=false and destructiveHint=false. Does not detail auth or rate limits, but sufficient given 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?

Three concise sentences, front-loaded with main action, no unnecessary words.

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 nested objects and complexity, description covers core behavior but lacks details on related tools (e.g., that drafts can later be shipped) and output format. Adequate for basic use.

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 100% with full descriptions for all 10 parameters. Description adds no extra parameter meaning beyond schema, baseline 3 applies.

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?

Description clearly states 'Create a draft parcel order', specifies it appears on Open Orders, does not purchase a label, and returns shipment_order_id. Distinguishes from siblings like deftship_ship_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 clear usage context: create draft, no label purchase, returns ID to update. Implicitly suggests use for drafts only, but lacks explicit when-not-to-use or alternatives beyond the ID update note.

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