pospal_set_product_stock_limit

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

The description discloses that it is a write operation and clarifies that it does not directly modify stock quantity. With no annotations provided, this is valuable behavioral context, though details on permissions or side effects are absent.

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?

A single sentence that is concise, front-loaded with purpose, and contains no unnecessary words. Every part earns its place.

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?

Despite having an output schema, the description lacks parameter explanations and does not cover return values or usage context. For a tool with three parameters, this is insufficient for complete understanding.

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 description provides no information about the parameters. With 0% schema coverage, the agent receives no guidance on what 'product_uid', 'min_stock', or 'max_stock' represent beyond their names.

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 indicates that the tool sets product stock upper and lower limits, distinguishing it from directly changing stock quantity. The verb '设置' (set) and resource '商品库存上下限' (product stock limits) are specific and unambiguous.

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 tells when to use the tool (to set stock limits) and explicitly states what it does not do (does not directly change stock quantity), implying that for direct stock changes, another tool should be used. However, it does not explicitly name alternatives or list when not to use this tool.

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