ubuntu_ssl_certificate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'manage' implies both read and write operations, it doesn't specify critical behaviors like whether actions are destructive (e.g., 'issue' might overwrite existing certificates), authentication requirements beyond SSH, rate limits for Let's Encrypt, or what the tool outputs. This leaves significant gaps for a tool with multiple action types.

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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded, with every word earning its place by conveying essential information about the tool's domain and technology stack.

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 complexity (multiple actions with different parameter requirements), lack of annotations, and absence of an output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., certificate paths, status messages, error formats) or provide context about Let's Encrypt integration, making it incomplete for effective agent use.

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 description coverage is 100%, so all parameters are documented in the schema. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't explain the relationship between 'action' values and other parameters like 'domain' or 'email'). Since the schema does the heavy lifting, the baseline score 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's purpose as managing SSL certificates using Let's Encrypt on Ubuntu, which includes both the verb ('manage') and resource ('SSL certificates'). It distinguishes itself from sibling tools like ubuntu_nginx_control or ubuntu_website_deployment by focusing specifically on SSL certificate operations, though it doesn't explicitly differentiate from all siblings.

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 versus alternatives. It doesn't mention prerequisites (e.g., needing an active SSH connection via ssh_connect first), nor does it explain when to choose this over other certificate management approaches or sibling tools like ubuntu_website_deployment that might handle certificates differently.

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