Install website SSL

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

The description substantially expands on the sparse annotations by revealing that setup runs in the background, returns immediately, progresses through `installing`/`active`/`failed` states, and is subject to multiple rate-limit and precondition errors including 422, 429, 403, and 404. This goes far beyond what annotations alone communicate.

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 tightly organized: core behavior first, then status reporting, then error conditions. Every sentence contributes operational value, and no filler or redundant restating of the tool name appears.

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?

For a two-parameter operation with no output schema, this description explains what happens after invocation, how to observe progress, all relevant error semantics, and rate limits. An agent has enough information to decide whether to call this tool and what to expect afterward.

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?

Both parameters are already fully documented in the input schema with 100% coverage, so the description does not need to add much. It confirms the domain is the subject of the certificate setup and the website UID is the target website, but adds no deeper formatting or relationship details beyond the schema.

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 opens with a specific action: 'Starts a Let's Encrypt certificate setup for the domain', clearly identifying the resource (the domain/website) and the operation (install SSL). It also clarifies that the tool returns immediately and runs asynchronously, distinguishing it from synchronous operations and related status/setup tools.

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 strong contextual guidance by explaining progress monitoring via `Get website SSL status` and `List website processes`, and delineates failure conditions with specific HTTP status codes. It does not explicitly name sibling alternatives like reinstall or uninstall, but the described behavior and constraints make the tool's role clear enough.

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