Publish site

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

Beyond the annotations, the description explains consent requirements, failure handling, and retry behavior. It makes clear that if the site cannot go live yet, nothing is published, Studio opens its Publish screen, and the agent must not call publish again when Studio finishes from that screen.

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 purpose and live URL outcome are front-loaded, followed by consent, failure, and retry constraints. Every sentence adds operational value, and the consent rule is stated emphatically enough to prevent accidental republishing.

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?

With no parameters and no output schema, the description carries the full burden and does so: it covers the action, destination, return value, consent gating, failure modes, and the correct follow-up when Studio takes over publishing. Nothing an agent needs in order to call it correctly 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?

The tool has zero parameters, so the schema requires no parameter documentation from the description. The description appropriately avoids parameter discussion and focuses on execution behavior and prerequisites.

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 states a specific verb and resource: publish the open site to Swebsy Hosting at its own swebsy.site address, returning the live URL. This clearly distinguishes the operation from site creation or editing siblings and tells the agent exactly what outcome to expect.

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 gives explicit gating rules: call ONLY after the user says yes in this conversation, ask again before every publish including a republish, and do not rely on an earlier yes. It also states what to do when publishing cannot proceed immediately and when Studio's Publish screen will finish the job.

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