hcloud_get_primary_ips_actions

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. The description adds essentially nothing beyond that — no scope (which resource's actions), no pagination behavior, no ordering defaults.

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 short, but the brevity comes from boilerplate, not from precision; the markdown anchor link (#tag/actions) is noise. The one useful idea (filtering via parameters) is buried in a vague second sentence.

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?

Five optional filter parameters and no output schema mean the description should at minimum state what collection is being listed and how results are returned. It says nothing about the primary-IP scope, leaving a genuine ambiguity with sibling list_actions tools.

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%, with detailed per-parameter docs for id, status, sort, page and per_page, so the schema carries parameter meaning. The description's generic 'URI parameters' phrase adds no information on top, but 3 is the correct baseline when the schema does the heavy lifting.

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 restates the name: 'List Actions' then 'Lists multiple [Actions]'. It never states the primary-IP scoping that the tool name implies, so an agent cannot tell it apart from hcloud_list_actions 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 is a tautology rather than a when-to-use rule. No mention of when to pick this over hcloud_list_primary_ip_actions or hcloud_get_action.

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