low_stock_report

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

With no annotations, the description carries the full burden of explaining behavior. It discloses that the tool 'Scans up to `scan` variants and filters locally,' including a performance tip to 'raise `scan` for a large catalogue.' This gives agents important context about potential limitations and how to adjust parameters accordingly.

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 just two sentences, yet conveys purpose, usage, parameter behavior, and a practical tip. It is tightly worded without redundancy, making it easy to parse quickly.

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 tool with no output schema and simple parameters, the description is essentially complete. It explains what is returned (variants at or below threshold), the sort order, and the parameter effects. A minor gap is not explicitly stating the output format, but that is not critical for this kind of report.

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?

The schema already fully covers both parameters with descriptions. The tool description adds further meaning by explaining the interaction: the threshold determines what qualifies as low stock, and the scan parameter controls how many variants are examined. This enriches the schema's static explanations.

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 tool's purpose: 'Variants at or below a stock threshold, lowest first.' This is a specific action (reporting) on a specific resource (variants). It distinguishes itself from sibling tools like search_products and check_inventory by focusing on low-stock items.

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 explicitly says 'Use for restock questions,' providing direct guidance on when to invoke this tool over alternatives. Though it doesn't name sibling tools, the use case is clearly differentiated from search/get/inventory operations.

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