get_low_stock_alerts

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

With no annotations provided, the description carries the full burden and does so well. It discloses the scanning behavior, the threshold condition (quantity <= threshold), the sort order (ascending by stock), and the exact return structure including field details. This is comprehensive for a read-only tool.

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 compact and well-structured: purpose first, then behavior, then alternatives, then return structure. Every sentence provides useful information with no fluff.

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 a single parameter and no output schema, the description covers all essential aspects: behavior, sorting, and return structure. It even details the fields within each alert, making it complete for an agent to understand the tool's output.

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 documents the threshold parameter with a description, and the tool description adds value by specifying the exact comparison operator (<=) and including threshold in the return dict. This clarifies the semantics beyond the schema's general 'below this value' wording.

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 retrieves a list of low-stock or out-of-stock SKUs at variant level with a customizable threshold. It uses a specific verb (取得) and resource (SKU list), and distinguishes itself from siblings by naming get_inventory_overview and get_stock_by_warehouse as alternatives.

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 points to alternatives for different needs: use get_inventory_overview for overall inventory stats and get_stock_by_warehouse for warehouse distribution. This gives clear direction on when to use this tool versus other inventory-related tools.

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