ssl_get_domain_acme_config

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

With no annotations provided, the description carries the full burden. It discloses that the operation is a read and mentions the optional impersonate behavior, which is useful. However, it does not describe what the returned configuration contains, whether any side effects occur, or what permissions are needed.

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 the core purpose, followed by a concise Args list. There is no filler or repetition of schema information beyond what is needed for clarity.

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 is simple with only two parameters and an output schema exists, so the description is minimally adequate. However, it does not explain what fields the ACME configuration contains, how it differs from the server-level ACME config, or when impersonation should be used. An agent could still select it correctly but may lack nuance.

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. It explains that 'domain' is a fully-qualified domain and that 'impersonate' is an optional user to act as. This adds meaning beyond the bare schema, though it remains fairly shallow and could specify formats or defaults more precisely.

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 verb ('Read'), a clear resource ('ACME configuration for a domain'), and names relevant providers (Let's Encrypt / ZeroSSL). This clearly distinguishes it from mutation siblings like ssl_set_domain_acme_config and from server-level tools like ssl_server_acme_config.

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 implies when to use the tool by saying it reads domain-level ACME configuration, but it does not explicitly state when this should be used over related tools such as ssl_list_domain_certs or ssl_server_acme_config. No exclusions or alternatives are mentioned.

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