hcloud_delete_certificate

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is known. However, the description adds zero behavioral context — no note on irreversibility, dependent resources, confirmation requirements, or what happens to certificates in use. It merely repeats the operation.

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 near-identical fragments ('Delete a Certificate' / 'Deletes a Certificate'), wasting the only sentence available on duplication rather than useful content. It is short but not efficient.

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 destructive one-parameter mutation with no output schema, the description should at minimum say what deletion entails and any failure/constraint conditions. With no annotations gap to compensate for on safety, the absence of any such detail leaves the definition incomplete.

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?

Only one parameter (id) exists and schema description coverage is 100%, with the schema itself stating 'ID of the Certificate.' Baseline 3 applies since the schema fully documents the input and the description need not elaborate.

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 text is a near-tautology: 'Delete a Certificate' restated as 'Deletes a Certificate.' While the verb and resource are identifiable, the description adds nothing beyond the tool name and does not differentiate from the many sibling delete tools (hcloud_delete_firewall, hcloud_delete_zone, etc.) or say what distinguishes deleting a certificate.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. It does not mention prerequisites (e.g., certificate must not be attached to a load balancer) or point to hcloud_list_certificates for discovering IDs, so the agent gets no routing help beyond the name.

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