zyxel_configure_interface

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

With no annotations provided, the description must fully disclose behavioral traits. 'Configure interface settings' only implies a mutation operation and provides no details on side effects, reversibility, required permissions, or interaction with existing configuration. This is a significant transparency gap.

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?

While the description is a single sentence with no wasted words, it is under-specified rather than concise. It does not convey enough information to justify its brevity, similar to the 'Process' example in the calibration.

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?

This is a mutation tool with five parameters, two enums, and no output schema. The description is completely inadequate in explaining what configuring an interface entails, what the parameters do in practice, or what the result of the operation is. The tool is far more complex than the description suggests.

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 all five parameters are already documented in the input schema. The description adds no additional context about parameter relationships or usage, but per the rubric the baseline is 3 when schema coverage is high.

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 'Configure interface settings' provides a clear verb ('configure') and resource ('interface settings'), but it is vague about what specific settings are addressed and does not distinguish it from the sibling tool 'zyxel_configure_switchport'. It is not a tautology, but it lacks precision.

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 description gives no guidance on when to use this tool versus alternatives like 'zyxel_configure_switchport' or 'zyxel_show_interfaces'. There is no context about prerequisites, connection requirements, or when this tool is the appropriate choice.

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