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

readOnlyHint=true already declares the safety profile, so the description only needs to add context. It does so by disclosing what the response contains (Sync Variants, print files, retail price), which is useful for a tool with no output schema. It stops short of noting pagination, error cases, or token-scope behavior beyond the schema.

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?

Two tight sentences plus the endpoint reference. The scope statement and the alternative-tool routing are front-loaded with no filler.

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?

With no output schema, the description usefully summarizes the returned object, and the sibling routing plus the underlying GET endpoint give an agent enough to call it correctly. Minor gaps (auth/token edge cases) are handled by the schema's store_id note, so little is missing.

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 both parameters (store_id, product_id with the @External-ID syntax) are documented in the schema itself. The description adds no parameter-level detail, so it earns the baseline 3 while the schema does the heavy lifting.

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 (Fetch) and resource (one product of a Manual-order/API store) and enumerates the payload (Sync Variants, catalog variant, print files, retail price). It explicitly names the sibling printful_get_sync_product as the tool for integrated stores, so an agent can disambiguate without opening either schema.

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?

Gives an explicit when-to-use-this (Manual-order/API store) and when-to-use-the-other (Shopify, Etsy, WooCommerce or other integrated store → printful_get_sync_product). The selection rule is stated outright rather than implied.

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