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

With no annotations, the description carries the full burden of behavioral disclosure. It adds valuable transparency by warning that content must be passed byte-for-byte and that minor changes can break inline scripts. This goes beyond the schema's basic description and alerts the agent to a critical constraint, though it doesn't discuss auth, reversibility, or 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?

The description is concise and front-loaded with the purpose, followed by critical usage guidance. The three sentences are dense but each earns its place: purpose, content-fidelity warning with alternative, and image handling. No filler or redundancy beyond the necessary emphasis on byte-for-byte fidelity.

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 the lack of an output schema, the description implicitly indicates the return is a 'shareable URL' but doesn't explicitly state the return format. It covers the main use case, the critical content-fidelity constraint, and a fallback for large content. Missing explicit return type and any auth/precondition notes, but the description is largely complete for a publish action.

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 parameters are already well-documented. The description largely reiterates the byte-for-byte instruction from the content param and mentions base64 images (already in schema). It doesn't add new syntactic or semantic details beyond the schema, so baseline 3 is appropriate.

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 a specific action: 'Publish HTML or Markdown content as a shareable URL.' It identifies the resource (content) and output (URL), which distinguishes it from sibling tools like publish_site that likely publish entire sites.

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 explicit guidance on when to use this tool versus the REST endpoint: 'If the content is too large to copy verbatim through the model, use the REST endpoint POST /v1/artifacts instead.' This provides a clear when-to-use and when-not-to-use condition, plus an alternative.

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