Remove Xpresso Graph Node

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

The description discloses that connections are automatically severed, which is important behavioral info beyond the name. However, it omits details like handle invalidation, undo behavior, or error conditions. Without annotations, more could be added.

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 concise sentences: first states the core action, second provides prerequisite and side effect. No filler; every sentence earns its place.

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 simplicity (1 required param, no output schema), the description covers handle acquisition, automatic connection removal, and references a sibling tool. Missing permissions or error handling, but still fairly complete for a delete operation.

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 schema provides a description for the handle parameter, but the description adds extra context: the handle must point to the target and how to discover its path id via list_xpresso_nodes. This adds meaningful guidance beyond the schema.

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 'Delete a GvNode from an Xpresso graph' and directly references the prerequisite tool list_xpresso_nodes. The title is consistent and distinguishes from sibling tools like remove_graph_node and list_graph_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?

It explicitly states when to use the tool and how to obtain the required handle, but does not exclude cases where other tools (e.g., remove_graph_node) might be more appropriate. However, the context is clear for Xpresso-specific deletions.

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