commerce_storefront_products_sync

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

The description explicitly adds scoping and auth context beyond the annotations: 'Routes through the platform's domain-agent dispatcher under your JWT, tenant, and company scope.' This is useful behavioral information. The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; no contradiction exists.

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 short and front-loaded, starting with the action being run, then the routing context, then the two parameters. There is no filler or redundant restatement of the schema defaults. It earns a high score for efficiency, though it sacrifices substantive detail.

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?

For a tool with 0% schema description coverage and a huge sibling list, the description is too thin. It never explains what storefront product syncing entails, when the agent should choose this tool, or what to put in the message/inputs. The output schema exists but does not compensate for missing selection and invocation guidance.

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 provides minimal glosses: message is 'Free-text objective' and inputs is 'Optional JSON string of structured inputs.' It does not explain what content the action expects, how the two parameters interact, or any example payload. This leaves the agent guessing about invocation 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 states a specific verb and resource: 'Run the commerce domain agent action `storefront_products_sync`.' It also clarifies that the tool routes through the platform's domain-agent dispatcher. However, it does not explain what the 'storefront_products_sync' action actually accomplishes or how it differs from sibling commerce tools such as commerce_catalog_sync or commerce_storefront_status.

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 guidance about when to use this tool versus alternatives like dispatch_domain_agent or other commerce_* actions. The description mentions routing and scope but does not state conditions, exclusions, or preferred use cases. An agent would have to infer usage from the tool name alone.

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