Evaluate & Replenish Low Stock

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

With no annotations, the description bears full responsibility for behavioral disclosure. It explains the evaluation logic, conditional order placement, default threshold, and safety of dryRun mode. It does not mention reversibility or side effects of placed orders, but the core behavior is transparent.

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 concise: four sentences covering purpose, logic, output, and dryRun. It is front-loaded with the key verb and resource, and every sentence adds value without redundancy.

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 the tool's moderate complexity (evaluation + order creation, 4 parameters, no output schema), the description is remarkably complete. It explains inputs, process, conditional behavior, default, and dryRun. The sibling tools provide further context for alternative actions.

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 baseline is 3. The description adds significant meaning beyond the schema by explaining the shortfall calculation (gap = last24h sales - on-hand), the role of gapThreshold, and dryRun as a safety toggle. This provides the agent with a holistic understanding of how parameters interact.

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 defines the tool's purpose: evaluate a single SKU across one or more stores, compute shortfall based on last 24h sales vs. on-hand, and automatically raise replenishment orders. It distinguishes itself from siblings by specifying the combined evaluation and ordering action.

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 explains when to use the tool (for evaluating low stock and ordering), mentions a default threshold, and highlights the dryRun option for safe testing. It does not explicitly state when not to use it, but the context is clear enough.

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