Create Replenishment Order

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

Without annotations, the description carries the burden and does well: it discloses validation, grouping by supplier, computing totals, and updating on-order quantities. This covers key mutation behaviors, though it omits details on error handling or rollback.

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 a single paragraph of three sentences, front-loading the purpose. Every sentence provides unique information without repetition, achieving high density of useful content.

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 creation tool with no output schema, the description covers core actions and mentions a 'confirmation with per-PO detail'. However, it lacks specifics on return format (e.g., order ID), error scenarios, prerequisites (store/SKU existence), and rate limits, leaving moderate gaps.

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%, so the baseline is 3. The description adds context like 'validates each SKU against the store' and 'groups lines by supplier', which are behavioral rather than parameter-specific. It does not enhance individual parameter meaning beyond the schema.

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 'Place' and resource 'replenishment (restock) order for one or more SKUs at a store'. It also details specific actions like validation, grouping, and updating, making it distinct from sibling tools like evaluate_replenishment.

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 when to use this tool (to place a restock order) and distinguishes it from siblings by focusing on creation vs. evaluation/inventory retrieval. However, it does not explicitly state when not to use or provide alternative scenarios.

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