hcloud_show_snapshot

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and repeatability are covered without help from the description. The description adds nothing beyond that — no note on error behavior for a nonexistent ID, no cross-region caveat, and no hint at response shape despite there being no output schema.

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?

It is a single tight sentence with the resource front-loaded and zero filler. It is arguably over-terse for a tool definition, but nothing in the sentence is wasted.

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 simple two-parameter read operation whose safety profile is fully covered by annotations and whose parameters are fully covered by the schema, so the description's burden is small. The only real gap is the unexplained 'EVS' acronym and lack of any pointer to the listing tool that produces the required ID.

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 both required parameters (region, snapshot_id) are documented in the schema, establishing the baseline of 3. The description contributes no additional meaning — it does not explain the region/snapshot_id relationship or any format expectations.

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 names a specific verb ('Get details') and resource ('EVS snapshot') and narrows scope to 'a specific' one, which implicitly distinguishes it from the sibling hcloud_list_snapshots. It does not explicitly name that sibling or state what fields the details include, so it stops short of full differentiation.

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?

'A specific ... snapshot' implies the caller must already hold a snapshot_id, which hints at a list-then-show workflow, but the description never says to use hcloud_list_snapshots first or when not to use this tool. Guidance is implied rather than stated.

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