publish_artwork_downloads

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the exported formats and that the links expire, but omits auth/permission requirements, whether any session state is modified, and how the expiration relates to the ttl_seconds parameter.

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?

A single front-loaded sentence with no filler. It leads with the verb and resource and efficiently packs formats, return type, and audience into one line.

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?

An output schema exists, so return values need not be explained in detail. However, with no annotations and 0% parameter description coverage, the description should do more to explain session_id and ttl_seconds and to distinguish this tool from nearby export siblings. It is adequate but has clear gaps.

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 both parameters. The description does not mention session_id or ttl_seconds at all; 'expiring' only vaguely hints at the TTL concept without explaining how to control it. The description fails to compensate for the undocumented 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?

States a specific verb ('Export') and resource ('final artwork') with concrete output formats (XCF, JPEG, PNG) and the return behavior (three expiring HTTPS links). It does not explicitly name or contrast with sibling tools like export_artwork or export_image, so it is clear but not fully differentiated.

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 phrase 'for external/autonomous clients' gives an intended usage context, implying when the tool is appropriate over file-only exports. However, it does not state when-not to use it or name any alternative sibling tool, leaving the routing decision partly to inference.

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