Remove Edge

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

Provides a key behavioral guarantee: removing an edge does not remove the nodes it joined. This helps the agent understand the side effects. No annotations exist, so this description carries the transparency burden and does so adequately.

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?

Two short sentences, no fluff. All information is relevant and directly supports the agent's decision-making.

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?

Sufficient for a simple edge-removal operation. It explains what, how, and a critical side-effect. It does not specify error conditions or output, but given the tool's simplicity and lack of output schema, this is acceptable.

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?

The description adds relational context beyond the schema by explaining that either edge_id or the source/target pair can be used, which is not immediately obvious from individual parameter descriptions. Schema coverage is 100%, so this is supplementary but valuable.

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?

States a specific verb ('Remove') and resource ('edge'), and clarifies the two ways the edge can be identified (by edge id or by source/target pair). This distinguishes it from sibling tools like remove_node or connect_nodes.

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?

Clearly implies when to use it (to remove an edge). It does not explicitly name alternatives or conditions when not to use it, but the purpose is unambiguous enough for an agent to select it appropriately among siblings.

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