Synchronize Micro products

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, so the core safety profile is covered. The description adds one useful behavioral guarantee—omitted remote products are not deleted—but does not disclose what acceptLiveProducts or acceptPriceChanges actually trigger. This is modest added context beyond the annotations, not a rich behavioral disclosure.

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 with no filler. The core behavior and the important non-deletion caveat are front-loaded, making it easy for an agent to parse quickly.

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?

The output schema covers return values, and annotations cover safety, but the description omits the semantics of two behavior-changing boolean flags. For a sync tool that may require accepting live products or price changes, this is a meaningful gap that could lead to incorrect invocation.

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 only 33%, with path documented but the two boolean parameters left unexplained. The description does not compensate: it never explains acceptLiveProducts or acceptPriceChanges, and 'declared products' only loosely hints at the sync source. The parameter meanings are largely left to inference from 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 states a clear operation—'Create or update declared products'—and adds the key boundary condition 'without deleting omitted remote products,' which distinguishes it from a destructive sync. It clearly identifies the resource (declared Micro products) and differentiates it from the related micro_products sibling.

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?

No guidance is given on when to use this tool versus alternatives such as micro_products or other product-related tools. There are no prerequisites or exclusion conditions; usage is only implied by the tool name and the word 'sync.'

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