hcloud_show_security_group

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. However, it only states 'Get details' without mentioning that the operation is read-only, what permissions might be required, or any potential side effects. The read-only nature is implied but not explicit, and no additional behavioral traits are disclosed.

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 sentence that efficiently conveys the tool's purpose. It is front-loaded and contains no extraneous words. Every word earns its place.

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 simple tool with two required parameters and no output schema, the description is minimally adequate. It explains the basic function but does not describe what 'details' are returned, any return format, or how the parameters relate to the result. Given the tool's simplicity, this is a borderline pass but could be enhanced with an example or return specification.

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% (both 'region' and 'security_group_id' are described in the schema). The description does not add any additional meaning or usage details beyond the parameter names and types. Baseline score of 3 is appropriate as the schema already documents the 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 'Get details of a specific security group' uses a clear verb ('Get') and resource ('security group'). It distinguishes itself from sibling tools like 'hcloud_list_security_groups' by specifying that it retrieves a single, specific group, not a list.

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 guidance is provided on when to use this tool versus alternatives. With many sibling 'list' and 'show' tools, the description does not explain, for example, that this tool is for fetching a single security group by ID, while 'hcloud_list_security_groups' retrieves all groups. No exclusion criteria or context for use is given.

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