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 for behavioral disclosure. It states the tool creates a link but doesn't mention whether this is a mutating operation (likely yes), what permissions are needed, whether links can be modified after creation, or what happens on failure (e.g., if nodes don't exist). The description adds minimal behavioral context beyond the basic action.

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 appropriately concise with two sentences: one stating the purpose and another listing key parameters. The structure is front-loaded with the main action. However, the parameter listing uses a comma-separated format that could be slightly clearer, and it doesn't group related parameters effectively.

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 (10 parameters, 3 required, 0% schema coverage, no annotations, but with output schema), the description is moderately complete. It covers the core action and some parameters but misses many others and behavioral aspects. The presence of an output schema helps, but the description should do more to compensate for the lack of annotations and poor schema documentation.

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%, so the description must compensate. It explains 4 parameters (node_a_id, node_b_id, adapter_a, port_a, adapter_b, port_b) with basic semantics, but ignores 6 others (project_id, server_url, username, password, and defaults for adapter/port parameters). The description adds value for some parameters but leaves most undocumented, resulting in partial compensation.

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 ('Create a link') and resource ('between two nodes'), which is specific and unambiguous. It distinguishes itself from sibling tools like 'gns3_delete_link' by being a creation operation rather than deletion. However, it doesn't explicitly differentiate from other connection-related tools that might exist in the broader context.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., nodes must exist), constraints (e.g., cannot link a node to itself), or comparison to sibling tools like 'gns3_list_links' for checking existing links. The agent must infer usage from the tool name alone.

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