graph_graph_add_edge

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

Description reveals the key behavioral trait that nodes are auto-created if they don't exist. However, it does not disclose whether the edge already exists (overwrite or error), permissions required, or other side effects. With no annotations, the description carries full burden but remains incomplete.

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?

Single sentence with clear action and context. The leading '[graph]' tag helps with categorization. No wasted words.

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?

Coverage is partial: it explains the core action and auto-creation, but omits prerequisites (graph must exist), error handling (duplicate edge), and any constraints. Output schema exists, so return values need not be explained, but preconditions are missing.

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 coverage is 0%, so the description must compensate. It only hints at 'src' and 'dst' via 'Add a directed edge src → dst', but does not explain the 'name' parameter (likely the graph name). The description adds minimal meaning beyond parameter names.

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: 'Add a directed edge src → dst' with the specific resource (edge in a graph) and direction. It also distinguishes from sibling tools like graph_graph_remove_edge and graph_graph_add_node by mentioning auto-creation of 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?

No guidance is provided on when to use this tool versus alternatives (e.g., graph_graph_add_node then a separate edge add, or graph_graph_remove_edge). The auto-creation hint is implicit but not explicitly compared to other tools.

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