Network interfaces

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds value by enumerating the data categories returned (MAC, link state, speed, IP, gateway, DNS, host name), which matters because there is no output schema, but it says nothing about pagination, empty results, or failure modes on unreachable controllers.

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?

A single front-loaded sentence with two parenthetical field lists — no preamble, no repetition, nothing to trim. Slightly dense, but every clause carries information.

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 parameters, the description is the only source of return-value information, and it names the concrete fields an agent will get. It falls short of 5 only because it doesn't note the two-part shape of the response (physical ports vs. iDRAC settings object) or behavior when a domain is unreachable.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly frames this as a whole-server snapshot rather than implying any filtering argument that an agent might otherwise try to supply.

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 uses a specific verb ('List') on two clearly named resources: the server's physical network ports and the iDRAC's own network configuration. It does not differentiate itself from a likely-overlapping sibling such as idrac_manager_info, which could also expose iDRAC network settings.

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?

Usage is only implied — an agent can infer 'call this when you need MAC/link/speed or IP/gateway/DNS data', but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative sibling for related manager configuration.

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