ssl_reissue_server

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

With no annotations, the description carries the full burden of disclosing behavior. It does state that the tool force-obtains/reissues a certificate via POST, but it omits important effects such as replacing the existing cert, service impact, irreversibility, or confirmation requirements beyond a vague 'confirm: Required'. This is insufficient for a mutating server-level operation.

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 short, action-first, and includes the endpoint and a clear use-case in compact form. However, the Args section is under-specified and the 'confirm: Required' claim conflicts with the schema, which slightly weakens the structural quality.

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 mutating server certificate operation with three parameters and no annotations, the description is incomplete. It does not explain two of the three parameters, does not warn about consequences of reissuing the hostname cert, and does not clearly contrast with the many sibling cert tools. The presence of an output schema helps but does not cover these gaps.

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 the parameters, but it only mentions 'confirm: Required' and ignores reason and idempotency_key. It also contradicts the schema: the schema shows confirm as optional with a default of false, while the description calls it required. This makes the parameter guidance confusing rather than helpful.

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 action ('Force-obtain / reissue') and the resource ('DirectAdmin hostname TLS certificate'), and confirms it with the specific endpoint 'POST /api/server-tls/obtain'. This distinguishes it from sibling tools like ssl_reissue_domain, which target domain certs rather than the hostname cert.

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 gives explicit conditions for use: 'Use this when the panel hostname cert is expired or the hostname changed.' It does not explicitly state when not to use it or name alternatives, so it stops short of a full decision guide.

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