Get catalog product

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the meaningful detail that variants are included in the response, but says nothing about failure modes for invalid ids, auth requirements, or response shape beyond variants.

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 tight sentence with the verb and resource front-loaded and zero filler. Nothing is repeated from the title and nothing extraneous is included.

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 single-parameter read tool with good annotations and no output schema, the description covers purpose, input identity, and the key return element (variants). Missing only a pointer to the discovery tool for obtaining a product id, which is a modest 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 description coverage is 0% for the single product_id parameter, so the description must carry the burden; it does partially by clarifying that the id is a *catalog* product id, which matters given siblings like list_sync_products and create_sync_product that use store product ids. It still omits format/validity details (positive integer, max value).

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 ("Get one Printful catalog product") plus the scope of what is returned ("including its variants"). It implicitly distinguishes itself from the search/discovery siblings by emphasizing "one" and "by catalog product id", though it never names an alternative.

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 explicit when-to-use statement and no named alternative such as search_catalog or get_variants. The phrase "by catalog product id" only weakly implies the caller must already know the id, leaving the discovery path (search first, then get) to inference.

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