graph_graph_remove_edge

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Remove a directed edge' but does not address edge cases (e.g., non-existent edge, graph not found), side effects, or return values. This is minimal 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 a single sentence with no extraneous text. It is front-loaded with the '[graph]' prefix consistent across sibling tools, making it easily scannable.

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 of graph operations and the presence of many sibling graph tools, the description lacks details on output, error handling, and usage context. Even with an output schema, the description does not explain return behavior or consequences.

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 input schema has 0% description coverage and the tool description adds no explanation for the three parameters (name, src, dst). An agent cannot infer meanings beyond the parameter names, which may be ambiguous (e.g., 'name' could be graph name or edge name).

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 verb 'remove' and the resource 'directed edge', distinguishing it from sibling tools like graph_graph_add_edge. However, it is minimal and does not elaborate on what constitutes a directed edge in this 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?

No guidance is provided on when to use this tool versus alternatives, such as graph_graph_add_edge or graph_graph_remove_node. There are no mentions of prerequisites or conditions under which removal is valid.

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