ssl_server_upload_files

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

The description does disclose key behavioral details: the operation replaces the certificate, 'confirm' is required, and 'force' permits an invalid certificate. However, with no annotations provided, the description carries the full burden and still omits side effects such as service impact, reversibility, or key-mismatch behavior for a sensitive mutation.

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 front-loaded: a single purpose sentence followed by a focused parameter list. There is no filler, and each line carries meaningful information for invoking the tool.

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?

The description covers the main purpose and parameter meanings, and an output schema exists so return values need not be explained. However, it lacks usage context, side-effect disclosure, and a clear definition of what 'confirm' should be set to, leaving an agent with ambiguity for a risky certificate-replacement operation.

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%, and the description compensates by explaining each parameter: certificate is a PEM cert with optional chain, key is a PEM private key, force allows an invalid cert, and confirm is required. It could be stronger by specifying the expected value/type for 'confirm', especially since the schema gives it a default of false but the description marks it as required.

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 first sentence names a specific action ('Replace'), a resource ('hostname certificate'), and an input format ('uploaded PEM files'), making the core purpose immediately clear. It does not explicitly distinguish this from sibling tools like ssl_upload_cert_files or ssl_server_certificate, but the 'hostname certificate' wording adds enough specificity.

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 the many SSL-related siblings, nor does it state prerequisites or exclusions. An agent must infer from the name and brief phrase that this is for hostname certificate replacement, and no alternatives are mentioned.

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