hcloud_get_primary_ip

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no note on what is returned, error behavior for a nonexistent ID, or the fact that it is a live API call; the markdown anchor to the OpenAPI tag is not 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?

It is very short and the purpose statement is front-loaded, with no padding. The trailing markdown documentation link consumes a sentence without informing an agent, which keeps it just under top marks.

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?

With no output schema, the description is the only place a caller could learn what a Primary IP resource contains or how the response is shaped, and it says nothing. Annotations and a fully documented single parameter make it minimally callable, but it is not genuinely informative.

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?

There is a single required parameter with 100% schema description coverage ("ID of the Primary IP", int64, min 1), so the schema already carries the parameter meaning. The description adds nothing further, which is the baseline-3 case rather than a failure.

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 reads "Get a Primary IP", which is a direct restatement of the tool name hcloud_get_primary_ip with no added specificity. It does not distinguish this single-resource fetch from siblings such as hcloud_list_primary_ips, hcloud_get_primary_ip_action, or hcloud_get_primary_ips_actions.

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 guidance on when to use this tool versus the many adjacent primary-IP tools (list, actions, update, delete, assign/unassign). The agent must infer from the name alone that this is a lookup by numeric ID.

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