add_item

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'ĐĂNG BÀI sản phẩm mới' (post a new product) without explaining side effects, permissions, rate limits, or validation behavior. This is insufficient for a write operation.

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 very concise at two sentences, with the main action front-loaded. However, the use of Vietnamese and the incomplete listing of parameters slightly reduce structural clarity. Overall, it is appropriately sized and each sentence adds value.

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 tool has 9 parameters (8 required) and no output schema, the description should explain return values and cover all parameters. It only partially addresses prerequisites and omits return behavior. The description is insufficiently complete for the tool's complexity.

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 description coverage is 0%. The description references only four parameters (category_id, image_id_list, logistics_channel_ids, attribute_list) by linking to sibling tools, which adds some meaning. However, it ignores the other five parameters (item_name, description, original_price, seller_stock, weight), leaving them completely unexplained. Thus, the description does not adequately compensate for the lack of schema descriptions.

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 action ('ĐĂNG BÀI' meaning POST) and resource ('sản phẩm mới' meaning new product), so the verb+resource is clear. However, the use of Vietnamese instead of English may reduce clarity for an AI agent. It partially distinguishes from siblings by listing required IDs from other tools.

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 lists prerequisites: category_id, image_id, logistics_channel_ids, attribute_list, and names the tools to call (get_category, upload_image, get_channel_list, get_attributes). This is good guidance on what to do before using this tool. However, it does not mention when NOT to use it or provide alternatives among the sibling tools.

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