list_cert_auto_certificates

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

The readOnlyHint annotation already discloses the safe read-only nature, so the description adds minimal extra behavioral context beyond scoping to the Certificate Manager account. It does not contradict the annotation, but it also does not disclose potential behaviors like pagination, result size limits, or empty-list behavior. This is adequate for a simple read-only list tool.

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 a single, front-loaded sentence with no wasted words. It immediately identifies the action, resource, and scope, which is ideal for an agent scanning tool definitions.

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 parameterless read-only list operation, the description is complete enough. It tells the agent exactly what will happen: all auto-certificates in the account will be returned. No output schema is needed to understand the basic purpose, and the available annotations and zero-parameter schema leave no critical gaps.

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 description does not need to explain any parameter semantics. The schema coverage is effectively 100% with no input parameters, and the description's mention of listing 'all' auto-certificates communicates the lack of filtering or pagination parameters.

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 ('all auto-certificates') within a clearly defined scope ('IONOS Cloud Certificate Manager account'). It is directly distinguishable from sibling tools like get_cert_auto_certificate, which implies fetching a single resource rather than listing all.

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 explicit guidance on when to use this tool versus alternatives, and no exclusions or conditions are mentioned. Usage is only implied by the 'List all' phrasing, but an agent is not told, for example, to use get_cert_auto_certificate when needing a single auto-certificate.

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