list_cert_certificates

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

The readOnlyHint annotation already signals a safe read operation. The description adds meaningful behavioral context by stating that the tool returns certificate metadata and public key material but not the private key, which is a useful and non-obvious disclosure. This goes beyond what annotations provide, though it does not cover potential pagination or ordering behavior.

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 two sentences with no filler. The core action is front-loaded, and the second sentence adds essential output detail. Every word earns its place.

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, read-only list tool with no output schema, the description covers the essential information: what is listed, what is returned, and what is not returned. Minor gaps like pagination or sorting are not explicitly mentioned, but the description is complete enough for an agent to select and invoke the tool correctly in most cases.

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, so the baseline is 4. The description correctly avoids inventing parameter guidance and focuses on the result. There is no parameter semantics gap because there are no parameters to document.

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 ('List') and resource ('SSL/TLS certificates in your IONOS Cloud Certificate Manager account'), making the tool's purpose clear. It also adds what is returned and excludes the private key, which helps distinguish it from other certificate tools. However, it does not explicitly differentiate from sibling list_cert_auto_certificates, so a slight ambiguity remains.

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 usage: when you need all SSL/TLS certificates in the account, this is the list tool to use. It does not explicitly name alternatives like list_cert_auto_certificates or get_cert_certificate, nor does it state when not to use this tool. The usage guidance is clear enough for a straightforward no-parameter list operation but is not explicit.

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