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

With no annotations, the description carries the full burden. It usefully discloses that the post becomes public (returns a 'public link') and that the full source must be supplied rather than a fragment, but omits auth/permission requirements, visibility of the source code itself, immutability, and rate limits.

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 short sentences, the action and its outcome are front-loaded, and the usage note follows. No wasted words, though the second sentence is a bare fragment.

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?

A mutation tool with no annotations and no output schema, whose description covers the observable return (a public link) but not permission requirements, publication side effects, or failure modes. Adequate minimum for a fully schema-documented 7-param tool, but not complete.

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 all 7 parameters are documented by the schema. The description only reinforces the code parameter ('complete source code') and adds nothing about community, kind detection, source, or remix_of, so 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 (publish) and resource (artifact on ArtiGram), and adds that the result is a public link. It does not explicitly distinguish the create path from the sibling update_artifact, leaving that inference to the agent.

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?

"Pass the complete source code" implies the required usage pattern, and the name implies creation rather than modification, but there is no explicit when-to-use/when-not or mention of update_artifact as the alternative.

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