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

readOnlyHint=true already covers the safety profile, and the description adds real value on top: it names the three possible status values (pending/completed/failed) and clarifies that image URLs only appear 'when done', implying polling semantics. It stops short of saying how often to poll or what failure responses contain.

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 front-loaded sentences that lead with the action and outcome, then cite the underlying endpoint. The 'Printful: GET /mockup-generator/task' fragment is mildly redundant but harmless and short.

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 carries the return-value burden and does it reasonably well by describing status values and the shape of the mockup URLs. Missing polling cadence and error/failure handling, but an agent has enough to call and interpret it.

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 100%, so both parameters (store_id, task_key) are already documented in the schema, including the token-scope nuance for store_id. The description adds no parameter-level detail beyond the workflow hint, so the baseline 3 applies.

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 (check) and resource (mockup-generation task), and concretely previews the output: status with its enum values plus per-placement/variant image URLs. This clearly separates it from the sibling printful_create_mockup_task, which starts the task rather than reading it.

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?

No explicit when-to-use or when-not-to-use statement, but the task_key schema note (returned by printful_create_mockup_task) and the 'when done' phrasing imply the create-then-poll workflow. Usage is inferable but never stated outright.

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