ecommerce_sync_multiplatform_stock

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

With no annotations provided, the description carries the full burden, but it only says 'sync stock and prices.' It does not reveal whether target values are overwritten, whether the operation requires source-to-target value flow, whether it is destructive, or what side effects it may have. This is minimal disclosure at best.

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 direct sentence with no filler or redundancy. It is front-loaded and readable, but it is so brief that it sacrifices useful detail for conciseness.

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's complexity — nested target objects, variant arrays, and optional newPrice/newStock fields — plus the absence of annotations and an output schema, the description is not nearly complete enough. It fails to explain how source data maps to target platforms, what the optional fields mean, or what 'sync' actually modifies.

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%, so the description must compensate, but it only broadly mentions stock and prices, giving almost no meaning to sourcePlatform, sourceProductName, targets, availableVariants, or the distinction between current and new values. Property names help, but the description adds insufficient semantic value for a nested input structure.

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 names a specific verb ('sync') and resource ('stock and prices') and adds a multi-platform scope that partially differentiates it from sibling tools like ecommerce_update_price_stock. However, it does not explicitly contrast with batch update or clarify the direction of synchronization, so it stops short of a 5.

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?

There is no explicit guidance on when to use this tool versus alternatives such as ecommerce_batch_update_price_stock or ecommerce_update_price_stock. The description simply restates the tool's basic function and leaves the selection context entirely to inference.

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