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

With no annotations provided, the description carries the behavioral disclosure burden. It adds useful context: the endpoint is free, it should only be used after task success, authentication for larger exports uses the same Bearer key, and there is a size ceiling that routes users to png_url. It does not fully explain response format or error behavior, but it covers the key operational traits.

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 with no redundancy. The main purpose is front-loaded, followed by usage timing and a clear alternative for larger exports. Every clause earns its place.

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 simple 3-parameter download tool with no output schema, the description is mostly complete: it states the return type, when to call it, the size-limit exception, and hints at authentication. More detail on the exact response body or explicit auth requirement for this endpoint would improve completeness, but nothing critical 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 67%, with width and variant already described in the schema. The description adds only indirect meaning to task_id by saying to use it after a task succeeded, and it indirectly references width limits by suggesting png_url for larger exports. This is adequate but not particularly rich beyond the schema.

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 tool returns a finished artwork as a PNG image, which distinguishes it from the sibling download_svg and download_logo_kit by format and scope. The phrase 'finished artwork' is slightly generic, but the overall purpose is specific and actionable.

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?

It explicitly says to use this tool after a task has succeeded, and it gives an alternative path for larger exports by using the png_url from the task result. It does not explicitly contrast with download_svg or download_logo_kit, but the when-to-use and the primary alternative are clearly stated.

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