pospal_update_product

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

The description indicates a write operation and partial update behavior. However, with no annotations, it lacks details on authorization, side effects, or return value. The 'only pass fields to modify' hint is useful but not comprehensive.

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, focused sentence that efficiently conveys the core purpose and key usage note. No wasted words.

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 presence of an output schema and a moderate number of parameters, the description is minimal. It does not explain return values or error handling, leaving some gaps for the agent.

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 0%, and the description does not describe any of the five parameters (name, enable, buy_price, product_id, sell_price). The general note about partial updates does not compensate for missing parameter-level details.

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 updates product fields (更新商品字段) and adds the important nuance that only fields to be modified should be passed. This distinguishes it from create and delete siblings.

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 instruction 'only pass fields that need to be modified' provides clear usage guidance for partial updates. It does not explicitly mention when to use this tool versus alternatives, but the resource name and context make it implicit.

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