check_ssl_certificates

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

No annotations are provided, so the description carries the full burden. It discloses the audit scope (host certificates, specifically Let's Encrypt / Certbot) and the exact return shape (JSON string with domains, expiration dates, days remaining, and warning flags). The verb 'Audit' implies a read-only operation, but it does not explicitly state that there are no side effects or mention any permission requirements.

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 two concise sentences: a clear purpose statement followed by a return-value summary. It is front-loaded and every sentence adds necessary information with no redundant text or filler.

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?

For a zero-parameter tool, the description is complete: it states the exact subject (host SSL/TLS certificates, Let's Encrypt / Certbot) and enumerates the return fields. An output schema reportedly exists, so return format does not need explanation. There are no missing invocation details.

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 has zero parameters, so the baseline is 4. There is no parameter meaning to add, and the description correctly avoids inventing parameters. Nothing is lacking on this dimension.

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 uses a specific verb ('Audit') with a clear resource ('SSL/TLS certificates configured on the host') and adds scope as Let's Encrypt / Certbot. It stands apart from all sibling tools, none of which target SSL/TLS certificate state, so an agent can confidently identify what this tool does.

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?

Usage context is implied by the tool's name and description: it is for auditing SSL/TLS certificates. However, there is no explicit statement of when to use this tool versus alternatives, nor any exclusion or comparison to sibling audit/health tools. That is implied usage, not explicit guidance.

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