update_addon_product

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

With no annotations, the description carries full burden. It labels the tool as WRITE, states changes take effect immediately, irreversibility but ability to overwrite, and provides return structure. This adequately discloses behavioral traits beyond simple read/write.

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 well-structured with clear sections (WRITE, 用途, API, return, side effects) and is front-loaded with the main action. Each sentence serves a purpose with no redundancy, though it could be slightly more concise.

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 two parameters with full schema coverage, a return structure specification, and side effect disclosure, the description is complete for an update tool. It lacks mention of authorization or permissible field constraints, but these are minor gaps in this context.

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 has 100% coverage for both parameters. The description adds value by explaining it is a partial update (only pass fields to change) and listing example fields (name, price, image). This provides meaningful context beyond the schema definitions.

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 'update addon product data' and lists specific fields like name, price, and image. It distinguishes from sibling tools like create_addon_product and update_addon_product_quantity, but could more explicitly differentiate when to use each.

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 includes a '用途' section advising to only pass fields to modify, providing basic usage guidance. However, it does not clarify when to use this tool versus alternatives such as update_addon_product_quantity or create_addon_product, missing explicit when-not or alternative recommendations.

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