graph_graph_remove_node

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

The description explicitly states that the node and all its edges are removed, which is a key behavioral detail. With no annotations provided, this is acceptable, though it could mention reversal or graph existence requirements.

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, efficient sentence that conveys the core functionality with no extraneous text.

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 lack of annotations and parameter descriptions, this minimal description is insufficient. It does not confirm that the graph must exist, nor does it describe the return value, even though an output schema exists.

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% and the description does not explain what the 'name' and 'node' parameters represent. The agent cannot know that 'name' likely refers to the graph name and 'node' to the node identifier.

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 (Remove) and resource (a node), with a domain prefix [graph]. It distinguishes from siblings like graph_graph_add_node and graph_graph_remove_edge by noting that all edges are removed.

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 given on when to use this tool versus alternatives such as graph_graph_remove_edge (which removes only an edge) or graph_graph_delete (which might remove the entire graph). The agent is left without decision support.

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