hcloud_list_certificates

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only 'Returns all Certificate objects', which is slightly misleading given the 7 filtering/pagination parameters and auto_paginate soft-cap — it does not disclose pagination behavior, the per_page maximum of 50, or that filters narrow the 'all' result.

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?

Extremely short and front-loaded, which is good, but the second sentence largely restates the title and wastes the only opportunity to add information. It is under-specified rather than efficiently concise.

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 seven optional filter/pagination parameters and no output schema, the description should at least point the agent at the available filters and the auto-pagination default. It leaves the agent to discover all of that from the schema, so the definition is thinner than the tool's complexity warrants.

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 100%, so every parameter (name, label_selector, type, sort, page, per_page, auto_paginate) is already documented in the schema and the baseline of 3 applies. The description adds no extra semantics about how filters interact with the 'all' claim.

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?

States a specific verb and resource ('List Certificates', 'Returns all Certificate objects'), so an agent knows exactly what resource is being enumerated. It does not distinguish this from the sibling hcloud_get_certificate (single-item fetch) or hcloud_list_certificate_actions, but the list-vs-get distinction is largely carried by the name itself.

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?

There is no guidance on when to use this versus hcloud_get_certificate or hcloud_list_certificate_actions, and no mention of preconditions or typical scenarios. Usage must be inferred entirely from the verb 'List'.

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