sites_publish

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states that it makes changes live, but does not mention side effects, reversibility, permission requirements, or what happens if no domains are specified. For a publish action with potentially significant consequences, this is insufficient.

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 two short sentences that directly state the tool's purpose and effect. There is no redundant or irrelevant information, making it highly concise and easy to parse.

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?

The tool has three parameters and no output schema, so the description should explain return values and edge cases. It does not mention what the tool returns, how it handles missing customDomains, or the significance of publishToWebflowSubdomain. The brief description leaves significant gaps for an agent trying to invoke it correctly.

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 schema already provides descriptions for all three parameters (site_id, customDomains, publishToWebflowSubdomain), so the description does not need to add parameter-level detail. The description adds no extra semantics, but the high schema coverage justifies a baseline score of 3.

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 uses a specific verb ('Publish') and resource ('site') with a clear scope ('to specified domains'), which clearly distinguishes it from sibling tools like sites_list and sites_get. It effectively communicates what the tool does.

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 provides context by stating that it makes the latest changes live, but it does not explicitly state when to use it versus alternatives or any exclusions. There are no sibling tools with similar publish functionality, so it is not misleading, but it lacks explicit usage guidance.

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