hcloud_get_certificate

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no mention of error behavior for unknown IDs, permissions, or what fields a Certificate object carries. For a read tool the bar is lower, but this text contributes essentially no new behavioral context.

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 text is short and front-loaded with the verb, but the second sentence merely paraphrases the first. It contains no waste in length yet also no information density – concise but under-specified.

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?

This is a single-parameter getter with full schema coverage, annotations, and no output schema, so the description needn't explain return values. Still, nothing tells the agent about sibling alternatives or failure modes, leaving the definition only barely sufficient for correct invocation.

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 coverage is 100% and the single id parameter is documented with type, range, and example (42), so the schema does the explanatory work. The description adds no naming or formatting guidance beyond what the schema provides, making 3 the correct baseline.

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?

"Gets a specific Certificate object" restates the tool name with modest added specificity (single object, not a list). It does not distinguish itself from close siblings such as hcloud_list_certificates, hcloud_get_certificate_action, or hcloud_update_certificate, so the agent must infer the boundary from the name alone.

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 statement of when to use this tool versus hcloud_list_certificates or hcloud_get_certificate_action, and no prerequisites such as authentication or required ID source. The only implied guidance is the word "specific", which the required id parameter already conveys.

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