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

The annotations already declare this as a non-read-only, destructive write operation. The description adds useful behavioral context by stating the order appears on the dispatch board, is unassigned, returns a new orderId, uses UTC times, and maps to POST /orders.

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 compact and front-loaded: write action, dispatch-board effect, unassigned state, return value, timezone, and endpoint. Every clause adds relevant information without unnecessary prose.

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 26-parameter creation tool with no output schema, the description usefully identifies the return value as the new orderId and clarifies the order's initial unassigned state. The full parameter documentation is handled by the schema, though richer notes on irreversible creation behavior could add value.

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?

With 26 parameters and 100% schema description coverage, the schema already explains the parameters in detail. The description adds that times are UTC, but the schema itself already documents UTC formats for the relevant time fields, so this remains baseline-level parameter guidance.

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 states a specific verb and resource: insert/create a new delivery order in Shipday. It also distinguishes the action from sibling assignment tools by noting that the created order appears on the dispatch board and is not assigned to a driver.

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?

It makes clear this is the creation action and implies assignment is separate, but it does not explicitly say when to use this versus querying, listing, or assigning orders. The usage context is present but mostly implied by the create semantics.

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