hcloud_show_user

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

The description indicates a read operation ('Get details'), but no annotations exist to confirm safety. No additional behavioral traits (e.g., authorization needs, rate limits, or side effects) are disclosed. For a simple read tool, the description is minimally adequate.

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 of 7 words, conveying the essential purpose without any extraneous information. It is front-loaded and 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 simple get-details tool with one parameter and no output schema, the description is reasonably complete. It covers the basic purpose, though it could mention the return format briefly. Given the existence of sibling tools with similar patterns, completeness is adequate.

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?

With 100% schema description coverage (user_id with 'User ID'), the description adds no new semantic meaning beyond the schema. The phrase 'specific IAM user' reinforces that the parameter identifies a user, but does not provide format or validation details.

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 IAM user' clearly states the action ('Get details') and the resource ('IAM user'), with 'specific' indicating it operates on a single entity. This distinguishes it from sibling tools like hcloud_list_users (which lists all users) and other show_* tools for different resources.

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 explicit instructions on when or when not to use this tool are provided. The naming convention (show_ vs list_) implies it for retrieving details of a specific user, but without explicit guidance, the agent must infer usage from sibling names.

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