ssl_install_self_signed

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

With no annotations provided, the description carries behavioral disclosure responsibility. It does disclose that confirmation is required, that overwrite replaces existing material, and that this is lab/placeholder only. However, it does not describe side effects such as whether the server is restarted, whether prior certificates are invalidated, or what the output response contains.

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 compact and well-structured: a one-sentence purpose followed by a labeled argument list. Every line adds information, and the key safety caveats are front-loaded.

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 has an output schema, the description does not need to explain return values. It covers purpose, usage context, and parameter semantics comprehensively enough for a 7-parameter tool with no annotations. Minor gaps like cert_id provenance and server-side effects prevent a perfect score.

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?

Schema description coverage is 0%, so the description must explain parameters, and it does. It documents all seven arguments, including key_type allowed values, dns_names defaulting to [domain], overwrite meaning, impersonate owner, and confirm being required. It adds meaningful value beyond the schema, though it could clarify how cert_id is obtained or how dns_names should be formatted.

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 states a specific verb and resource: 'Install a self-signed certificate on a domain (lab / placeholder only).' This clearly distinguishes it from SSL siblings like ssl_reissue_domain or ssl_delete_domain_cert by focusing on self-signed installation. The lab/placeholder qualifier further narrows intent.

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 parenthetical '(lab / placeholder only)' provides clear context about when this tool is appropriate and explicitly excludes production use. It does not name alternative tools or provide when-not-to-use guidance beyond the lab caveat, so it stops short of a 5.

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