Setup SSL Certificate (Certbot)

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

The description adds valuable behavioral context beyond annotations: it generates a 2-step plan, uses OS-specific package mapping, and tests auto-renewal. This contrasts with the destructiveHint annotation by clarifying it is a planning tool, not directly mutating. No contradiction with annotations.

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?

Two sentences, concise and front-loaded with the core purpose, followed by key capabilities. No redundant information.

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 tool's simplicity (0 required params, no output schema), the description covers essential aspects: plan generation, OS mapping, and auto-renewal testing. It is clear and sufficient for an agent to understand what the tool does, though it lacks details on how to execute the generated plan.

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 fully described in the input schema (100% coverage), including fallback to .devops-mcp.json. The description does not add new semantic information about parameters, meeting the baseline expectation.

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 it generates an execution plan for installing Certbot and configuring Let's Encrypt SSL for Nginx, specifying the verb 'generates' and the resource 'SSL certificate for Nginx using Certbot'. However, it does not explicitly distinguish itself from sibling tools like setup_nginx_reverse_proxy, which is a separate but related task.

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?

No explicit guidance on when to use this tool versus alternatives or prerequisites. The description implies it is for planning an SSL setup, but does not state conditions or provide 'when not to use' context.

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