raise_replenishment_order

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

Without annotations, the description correctly labels the tool as write action and warns about confirming quantity. However, it does not disclose potential side effects, required permissions, or error conditions. It states return value partially (order_id, status) but no details on format. This is minimal transparency.

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?

Description is concise (3 sentences), front-loaded with the core action, and includes a necessary caution. Every sentence adds value.

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?

The description identifies the action, return value, and caution. However, it does not mention preconditions like store or SKU existence, or what 'on behalf of Korral' means. Given 5 parameters and no output schema, more context about the order creation process would be helpful.

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 already describes all 5 parameters with 100% coverage. The tool description adds no additional parameter semantics beyond restating 'SKU' and 'store'. Baseline 3 is appropriate.

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 uses specific verb 'Place' and resource 'replenishment order', and defines scope (SKU, store). It clearly differentiates from siblings which are read-only or status-checking tools.

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 implies usage when needing to create an order, but does not provide explicit guidance on when not to use or how it compares to siblings like replenishment_order_status or sku_report.

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