Set up nginx reverse proxy + Let's Encrypt SSL

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

No annotations are provided, so the description carries full burden. It discloses that the tool installs software and modifies configuration, which implies system-level changes. However, it does not explicitly state that existing nginx configurations may be overwritten or that the tool requires root privileges.

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 sentences long, front-loaded with the core purpose, and every word adds value. No redundant or verbose phrasing.

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 setup tool with 8 parameters and no output schema, the description covers the essential workflow and prerequisites. It is sufficient for an agent to determine when to invoke this tool and what it accomplishes, though details on post-execution state are omitted.

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 input schema has 100% description coverage, so the schema already explains each parameter well. The description adds minimal extra context beyond the prerequisites. The baseline of 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 the tool installs nginx and certbot, configures a reverse proxy, and obtains a Let's Encrypt SSL certificate. These specific actions distinguish it from sibling tools like deploy_docker_compose or exec, which have different purposes.

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 explicitly specifies prerequisites: DNS A record must point at the server and ports 80/443 must be open. This tells the agent when the tool can be used, though it does not directly mention when not to use it or suggest alternatives.

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