panelica_ssl_post_v1_ssl_domains_domain_id_issue

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

Annotations already indicate this is not read-only, so the description's explicit 'Mutating: changes server state' adds useful confirmation of side effects. It also states the required scope `ssl:write`, but it does not disclose potential validation delays, rate limits, or failure behavior of Let's Encrypt issuance.

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, with each line adding distinct information: action, HTTP endpoint, category, required scope, and mutating behavior. It is slightly redundant with the tool name's endpoint, but there is no 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?

The tool has no output schema and an open, undeclared request body, yet the description does not explain what the body should contain, whether issuance is synchronous or asynchronous, or what prerequisites must be satisfied. For a live certificate issuance action, this is a significant gap.

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 100%, which sets the baseline at 3, but the actual descriptions are thin: `domain_id` is only identified as a path parameter and `body` is an open object with no declared schema. The description adds no further meaning about required body fields or their semantics.

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 opens with a specific verb and resource: 'Issues a Let's Encrypt SSL certificate for a domain.' This clearly states the action and target, and the word 'Issues' plus 'Let's Encrypt' distinguishes it from the sibling renew and upload endpoints.

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 when-to-use or when-not-to-use guidance. It does not mention alternatives such as renew or upload, nor does it explain prerequisites like domain validation or DNS setup before issuing a certificate.

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