hcloud_list_primary_ips

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

The annotations already declare read-only, open-world, and non-destructive behavior. The description adds only a generic note about URI parameters and does not disclose return behavior, pagination semantics, or filtering behavior beyond what the schema already provides.

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 brief and front-loads the core purpose. However, it spends lines repeating the same idea ("List Primary IPs" then "List multiple Primary IPs") and includes a mostly generic sentence about URI parameters.

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?

The tool has no output schema and seven fully documented input parameters. The description does not explain the response shape or how auto-pagination behaves, but for a simple list operation the schema plus annotations cover most of what an agent needs.

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 the schema already documents all seven parameters in detail. The description merely says URI parameters modify the result and adds no meaningful syntax, filtering, or pagination semantics beyond the schema, making the baseline 3 appropriate.

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 clearly states a specific verb and resource: "List Primary IPs" / "List multiple Primary IPs." It is distinguishable from the singular sibling `hcloud_get_primary_ip`, but it does not explicitly name or differentiate itself from related tools such as `hcloud_get_primary_ip` or `hcloud_list_primary_ip_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?

The only guidance is "Use the provided URI parameters to modify the result," which does not explain when to use this tool versus `hcloud_get_primary_ip` or other primary-IP-related siblings. There are no exclusions or selection criteria provided.

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