ssl_server_status

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

No annotations are provided, so the description must carry the behavioral burden. It does not disclose whether this is a read-only status check, what specific TLS status it reports, whether it inspects the certificate, or what side effects might occur. The word 'status' weakly implies a read operation, but that is not enough for a no-annotation tool.

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, compact sentence that immediately states the target resource and the key exclusion. It is front-loaded and contains no filler or redundant phrasing.

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 no-argument tool with an output schema available, this description is mostly sufficient: an agent knows the target is server-level TLS status, not a user domain. However, it does not explain what kind of status information is returned or when this status check is appropriate, leaving some context gaps despite the simple signature.

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 tool takes zero parameters, so the baseline is 4 and parameter explanation is unnecessary. The description adds no parameter details, but none are needed for correct invocation.

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 identifies the resource as the hostname/DirectAdmin service TLS status and explicitly scopes it away from user domains, which helps distinguish it from domain-level SSL tools. However, it lacks a specific verb like 'get' or 'retrieve,' so it reads as a noun phrase rather than a clear action.

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 phrase 'not a user domain' provides a useful exclusion, implying this is for server-level TLS checks rather than user domain certificates. But it does not explicitly say when to use this tool versus alternatives like ssl_server_certificate or ssl_server_files, and no alternatives are named.

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