Publish artifact

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

No annotations provided, description carries full burden. Describes live vs snapshot behavior, remote vs local behavior. Does not disclose error handling, capacity limits, or exact return format. Adequate but not exhaustive.

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?

Three sentences, each valuable. Front-loaded purpose, then usage, then technical constraint. No redundant information.

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 no output schema and 8 parameters, description covers core purpose and key usage but lacks mention of return value (URL) and error scenarios. Adequate for typical use but not fully comprehensive.

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 38%; description adds meaning: explains live parameter, updateExisting usage, source types (path, content, folder), and slug generation. Compensates for schema gaps but not fully for all 8 parameters.

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 (publish), resource (artifact shelf), and output (stable browser preview URL). It distinguishes from siblings artifact_delete and artifact_list by specifying the action of publishing viewable content.

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?

Provides explicit when-to-call: whenever producing viewable content so user gets a URL without asking. Mentions using same slug with updateExisting:true for revisions. Notes path/folder sources vs remote content sources. Lacks explicit when-not-to-call but context is clear.

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