hcloud_list_public_ips

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

With no annotations, the description must disclose behavioral traits. It only states 'List elastic public IPs', omitting whether the operation is read-only, what data it returns, pagination behavior, or any side effects. This is insufficient for an agent to understand the tool's full behavior.

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 short sentence with no wasted words. It is concise and front-loaded, but it sacrifices completeness. Given the tool's simplicity, this is appropriate, though additional context would improve it.

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 description lacks an explanation of the output format (since no output schema), which is critical for a list tool. It also does not clarify the region parameter's expected format or the effect of the limit parameter. This incompleteness, combined with the many sibling tools, leaves the agent underinformed.

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 'limit' have descriptions), so the schema already documents the parameters. The description adds no extra meaning, meeting the baseline of 3.

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 'List elastic public IPs' uses a clear verb+resource structure, specifying the resource type (public IPs) which distinguishes it from other list tools like hcloud_list_servers. However, it does not explain what 'elastic' means or the scope of the list (e.g., all IPs for the account?), limiting clarity.

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 siblings like hcloud_show_public_ip (for a single IP) or other list tools. The description does not mention prerequisites, use cases, or alternatives, leaving the agent to infer context from the tool name alone.

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