Create Consignment with Existing Saved Items

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds essentially no behaviour beyond that: nothing about what happens when a referenced item ID/SKU is not found, whether the consignment is created atomically, or that a write to a live carrier environment occurs (openWorldHint=true).

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 purpose is front-loaded in one sentence with no filler. The trailing 'Args:' block largely restates what the schema already declares about 'consignment', making it mild redundancy rather than an asset.

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?

An output schema exists, so return values need not be explained. However, this is a write operation whose entire payload is an undocumented free-form nested object; the description gives no guidance on payload structure and does not point the agent at a schema-discovery tool such as machship_get_custom_schema or the sibling create tools for the expected consignment shape.

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 nominally 100% for the single 'consignment' parameter, so the baseline of 3 applies. In practice the schema is an empty additionalProperties object, so the description's note that it references existing saved item IDs is the only real meaning conveyed; it adds nothing about which fields are required or how item references should be shaped.

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?

States a specific verb and resource ('Creates a consignment') plus the defining constraint 'using previously saved company items (by item ID / SKU)', which lets an agent distinguish it from machship_create_consignment and machship_create_consignment_with_complex_items. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied: use this when the items already exist as saved company items and you can reference them by ID or SKU. There is no explicit when-not guidance, no mention of the alternative creation tools, and no stated precondition (e.g. that item IDs must already exist in the company) or failure behaviour for unknown IDs.

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