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

Annotations already grant readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description's 'Read only' plus the enumeration of returned fields (enabled state, cadence, last-run, product count) adds return-value context the annotations do not provide, which is valuable given no output schema 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?

One sentence, zero filler, front-loaded with the primary subject and closing with the read-only qualifier. Every clause earns its place.

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 simple read-only status tool with one documented param and no output schema, the description adequately conveys what will be returned. The absence of any routing guidance versus mutation siblings is the main residual gap.

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% and the single 'site' parameter is fully documented in the schema, so the description adds no parameter detail beyond it. Baseline 3 is appropriate when the schema does all the param work.

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 resource (Shopify product sync status) and enumerates exactly what is reported: on/off, run frequency, last run time, and product count. It is distinguishable from write siblings like sync_products and update_product_sync_settings, though it never names them explicitly.

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 when-to-use guidance and no distinction drawn against sibling tools such as sync_products (which triggers a run) or update_product_sync_settings (which mutates). The agent must infer the read-only framing on its own, which is the only hint at appropriate usage.

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