ssl_acme_dns_providers

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 correctly implies a non-destructive read operation by using 'List', and 'the panel knows about' suggests the data is locally known rather than fetched live. However, it does not disclose response characteristics such as whether the list can be empty or whether any provider-specific details are included.

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?

A single sentence that front-loads the action and object, with no filler or repetition. The parenthetical example adds practical value without bloating the description.

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-parameter enumeration tool with an output schema present, the description gives sufficient context to invoke it correctly. It could have mentioned how the result feeds into ACME DNS-01 configuration, but that is not required to call the tool.

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 has zero parameters and an empty input schema, so the schema already covers everything. The description's example 'Cloudflare' is illustrative but unnecessary for parameter understanding, which is why the baseline for zero-parameter tools applies.

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 clear verb ('List') and a specific resource ('ACME DNS-01 providers the panel knows about'), plus an example ('Cloudflare'). This makes the tool easily distinguishable from the many ssl_* sibling tools without needing to inspect 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 purpose is obvious: it enumerates the DNS-01 providers supported by the panel, which is the natural discovery step before configuring ACME DNS-01. It does not explicitly list alternatives or exclusions, but with zero parameters and a generic listing purpose the context is clear enough.

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