GNS3 Network Simulator MCP Server

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether this requires authentication, potential side effects (e.g., temporary disruption), rate limits, or what the output contains. For a mutation tool (reload implies state change), this is a significant gap in transparency.

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 (one sentence) and front-loaded with the core action. Every word earns its place, with no wasted text, 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 mutation tool with 5 parameters, 0% schema coverage, and no annotations), the description is incomplete. While an output schema exists (which helps), the description lacks crucial context about authentication needs, error conditions, and parameter meanings, making it inadequate for safe and effective 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 0%, meaning none of the 5 parameters are documented in the schema. The description provides no information about parameters beyond what's implied by the tool name (node). It doesn't explain what 'project_id', 'node_id', 'server_url', 'username', or 'password' mean or how to use them, failing to compensate for the schema gap.

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 action ('reload a node') and clarifies what reload means ('restart without stopping'), which distinguishes it from stop/start operations. However, it doesn't explicitly differentiate from siblings like 'gns3_start_node' or 'gns3_restart_node' (if such exists), though the clarification about 'without stopping' helps.

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 like 'gns3_start_node', 'gns3_stop_node', or 'gns3_restart_node' (if applicable). The description only explains what the tool does, not when it's appropriate compared to other node control tools in the sibling list.

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