ubuntu_ssl_certificate

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

No annotations are provided, so the description must disclose behavioral traits. It doesn't mention that this tool modifies the server's certificate store, requires root/sudo, or makes network requests to Let's Encrypt. The vague verb 'Manage' gives no safety or side-effect information.

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 one short sentence, making it concise and front-loaded. However, it is so generic that it borders on under-specification, repeating the tool's name without meaningful value. It earns a middle score for brevity but lacks substance.

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 output schema and no annotations, the description is the only narrative source for expected behavior. It doesn't explain return values, error conditions, or effects on the system. The schema helps with parameters, but the description is insufficient for a tool that can issue and renew certificates.

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 documents all six parameters with descriptions (100% coverage), so parameter semantics are already provided programmatically. The description adds no additional meaning beyond what the schema contains.

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 identifies the resource (Let's Encrypt SSL certificates on Ubuntu) and implies management operations, but the verb 'Manage' is broad and doesn't specify concrete actions like issue, renew, status, or list. It is clear enough to distinguish from sibling tools (which handle SSH, nginx, firewall), but lacks precision for a high score.

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 no guidance on when to use this tool instead of alternatives like ubuntu_nginx_control or ssh_exec. It doesn't mention prerequisites (e.g., domain DNS pointing to server, HTTP server running for webroot validation) or exclude any cases.

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