printify_upload_image

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals a key server-side behavior: Printify fetches the image from the provided URL, which is why local paths fail. This goes beyond the schema by explaining the underlying mechanism. It does not mention overwrite behavior or return values, but for a simple upload tool the critical failure mode is disclosed.

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 sentences, front-loaded with the tool's purpose, and the second sentence delivers the key constraint. Every word earns its place with no redundancy or 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?

For a two-parameter upload tool with no output schema or annotations, the description covers the essential workflow: upload to media library for later product placement, and the URL requirement. It does not describe the return value or how to reference the uploaded image, but the core invocation knowledge is complete enough for an agent to make a correct call.

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%, so the schema already documents both parameters. The description adds meaning to the 'url' parameter by explaining why it must be publicly reachable — Printify fetches it server-side — and explicitly warns against local paths. This is a meaningful addition beyond the schema's own field descriptions.

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: 'Upload artwork to the Printify media library so it can be placed on a product.' This clearly differentiates the tool from its siblings, which are mostly get/list/publish operations. No other sibling handles uploading media, so the purpose is unmistakable.

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 gives clear context: upload artwork before placing it on a product, and use a publicly reachable URL. It also provides an explicit exclusion by warning that 'a local file path will not work.' However, it does not explicitly name alternative tools or state when not to use this tool beyond the URL limitation.

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