hcloud_list_server_interfaces

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

No annotations are provided, so the description carries the full burden. It only says 'List network interfaces', implying a read operation, but does not disclose any behavioral traits such as required permissions, error conditions, or return behavior (e.g., empty list if none).

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 with no wasted words, perfectly concise for a straightforward list tool.

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 and no annotations, the description lacks completeness. It does not explain what information is returned (e.g., MAC address, IP, status), which is critical for an agent to interpret the result. The description is insufficient for a tool without supplementary structures.

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 coverage is 100% with both parameters having basic descriptions ('Region', 'Server ID'). The tool description adds no further meaning beyond what the schema already provides, resulting in no added value. Baseline 3 is 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 the tool lists network interfaces attached to an ECS server, which distinguishes it from sibling tools like hcloud_list_servers or hcloud_list_volumes. However, it does not specify that it's for a single server or clarify the scope (e.g., all interfaces for the server).

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 others, nor are there any prerequisites or conditions for use. For example, it does not state that the server must exist or what happens if there are no interfaces.

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