Get a catalog product

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds useful context about the returned data (variants, placements) but does not disclose any additional behavioral traits such as rate limits, authentication requirements, or response format. Since the annotations carry the main safety burden, a 3 is appropriate for the marginal added value.

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 a single, well-structured sentence that front-loads the action and resource, then lists the key data components. Every part adds value, with no redundancy or filler. It is appropriately sized for a simple fetch operation.

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?

Given there is no output schema, the description provides a good overview of what the tool returns (variants, blanks, sizes, colours, print placements). It does not mention error conditions or authentication, but for a read-only fetch by ID, these are less critical. The description is sufficient for an agent to understand the tool's scope and expected result.

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?

The input schema has only one parameter 'id' with basic type constraints, and the description does not explicitly explain that 'id' refers to the catalog product ID. Although this is implied by the tool name and resource type, the description adds no direct value over the schema. With schema coverage at 0%, the description should compensate, but it only indirectly hints at the parameter's meaning.

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 clearly states the verb 'Fetch', the resource 'Printful catalog product', and explicitly lists what is included: variants, blanks, sizes, colours, and print placements. This distinguishes it from siblings like printful_get_store_product by specifying the catalog scope, so an agent can select it correctly without ambiguity.

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?

The description implies when to use it by naming the resource type (catalog product), which contrasts with store products. However, it does not explicitly state alternatives or exclusions. The context is clear enough for an agent to infer that this is for catalog items, but it could be improved by explicitly mentioning that store-specific products should use printful_get_store_product instead.

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