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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the call blocks ('Slow: it waits for the whole sync') and returns counts. It stops short of noting permissions or what happens on partial failure.

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?

Three short sentences, zero filler, with the core action and scope front-loaded and the alternative routing placed last where it belongs.

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?

No output schema exists, and the description compensates by stating it returns counts. Combined with the blocking-behavior warning, scope restriction, and alternative routing, an agent has what it needs; only auth/permission prerequisites are unstated.

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 coverage is 100% with only one parameter, so the schema already documents 'site' including the allowed value. The description's 'Shopify sites only' adds a small constraint on what site is valid, but nothing about format or identity beyond the schema.

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?

States a specific verb (syncs/pulls) and resource (Shopify products into the catalogue) plus a scope qualifier ('Shopify sites only'). It is immediately distinguishable from siblings like get_product_sync_status or update_product_sync_settings.

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?

Explicitly frames the tool as a run-it-now manual sync and routes scheduled syncs to the named alternative update_product_sync_settings. The 'Shopify sites only' restriction further tells the agent when this tool is inapplicable.

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