NetworkX Graph MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Remove an edge' implies a destructive mutation, but it doesn't specify whether this operation is reversible, what permissions are required, how errors are handled (e.g., if the edge doesn't exist), or what the response looks like. For a mutation tool with zero annotation coverage, this is a critical 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?

The description is extremely concise with a single three-word sentence. It's front-loaded and wastes no words, though this brevity comes at the cost of completeness. Every word earns its place, making it structurally efficient despite being under-specified.

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 tool's complexity (a destructive mutation with three parameters), lack of annotations, 0% schema description coverage, and no output schema, the description is completely inadequate. It doesn't explain what an edge is, how removal affects the graph, what happens on success/failure, or provide any operational context. This leaves the agent with insufficient information to use the tool correctly.

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 three parameters (graph_id, from, to) are documented in the schema. The description adds no information about what these parameters mean, their expected formats, or how they relate to edge removal. For a tool with three required parameters and no schema documentation, the description fails to compensate.

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 'Remove an edge' is a tautology that restates the tool name without adding meaningful context. While it specifies the verb 'remove' and resource 'edge', it doesn't distinguish this tool from sibling tools like 'remove_node' or explain what constitutes an 'edge' in this graph context. The purpose is minimally stated but lacks differentiation.

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. It doesn't mention prerequisites (e.g., needing an existing edge), exclusions, or relationships to sibling tools like 'get_edges' (to check edges first) or 'bulk_add_edges' (for batch operations). Without any usage context, the agent has no basis for decision-making.

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