pve_apply_node_network

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

With no annotations, the description carries full burden but provides minimal behavioral insight. 'Apply network changes' implies a write/mutation operation, but it doesn't disclose critical traits like whether it requires admin permissions, if it causes network downtime, what happens on failure, or if it's idempotent. The parenthetical '(reload config)' hints at reloading configuration, but this is insufficient for a mutation tool with zero annotation coverage.

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 extremely concise—just two words plus a parenthetical—with zero wasted text. It's front-loaded and to the point, making it easy to parse quickly.

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?

Given the complexity (a network configuration mutation tool), lack of annotations, and no output schema, the description is incomplete. It fails to explain the tool's behavior, side effects, error conditions, or what 'apply' means operationally. For a tool that likely impacts system networking, this is a significant gap in providing enough context for safe use.

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% (the 'node' parameter is documented as 'Node name'), so the baseline is 3. The description adds no additional meaning about the parameter—it doesn't explain what a 'node' is in this context or how to identify it, but the schema already provides the essential info.

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 'Apply network changes (reload config)' states a verb ('apply') and resource ('network changes'), but it's vague about what 'apply' entails—does it commit pending changes, restart services, or something else? It doesn't differentiate from siblings like 'pve_update_node_network' (which likely modifies config) or 'pve_revert_node_network' (which undoes changes), leaving ambiguity.

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 alternatives. For example, it doesn't specify if this should be called after 'pve_update_node_network' to activate changes, or if it's safe to use during network operations. The description lacks context about prerequisites or exclusions.

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