ecp_ssl_request_lets_encrypt

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

No annotations are present, so the description carries the behavioral transparency burden. It does disclose a meaningful side-effect boundary by stating it does not apply the certificate to nginx. However, it does not describe what success looks like, whether the issuance is synchronous, whether existing certificates are replaced, or what preconditions such as domain validation may be required.

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 one sentence, front-loaded with the main action, and contains a compact parenthetical that clarifies the non-effect and directs to relevant alternatives. There is no filler or redundant restatement of the tool name.

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 tool with one parameter and no output schema or annotations, the description gives enough orientation to know what happens and what the next-step sibling tools are. Still, it does not describe expected return behavior, issuance timing, potential failures, or prerequisites like domain reachability or DNS validation, so an agent could not fully anticipate the outcome.

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 compensate. The phrase 'for a domain' clarifies that the single required parameter is the target of the issuance, which adds a small amount of meaning beyond the parameter name. But it does not explain the expected format, validation requirements, or any practical restrictions beyond what the field name already implies.

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 states a specific action: 'Issue a new Let's Encrypt certificate for a domain.' It also distinguishes itself from the self-signed and apply/update tools by naming 'Let's Encrypt' and explicitly carving out the apply step. An agent can tell it apart from ecp_ssl_request_self_signed and ecp_ssl_apply_certificate without opening their schemas.

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 an explicit when-not and names alternatives: 'does not apply it to nginx - see ecp_ssl_update_lets_encrypt or ecp_ssl_apply_certificate.' It clearly routes an agent that needs an applied certificate to the right siblings, though it does not differentiate precisely when to choose update_lets_encrypt versus apply_certificate.

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