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

Even though annotations already mark this as destructive and non-read-only, the description adds valuable behavioral detail: the logic chain is automatically re-linked, start/end nodes are protected, and user confirmation is required before execution. This goes well beyond what the annotations alone communicate.

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?

Four short sentences, each earning its place: the action, the re-linking behavior, the valid-target exclusions, and the confirmation requirement. It is front-loaded with the core purpose and contains no filler or repetition of schema descriptions.

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?

For a destructive 4-parameter tool with no output schema, the description—combined with the annotations and detailed confirm parameter—covers what an agent needs to call it safely and correctly: target, side effects, invalid targets, and confirmation behavior. Nothing critical is 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?

The schema already provides 100% parameter coverage, giving a baseline of 3. The description adds useful parameter-level constraints for node_id by stating that start nodes and the last end screen cannot be deleted, and it reinforces the meaning of the confirm parameter by requiring explicit confirmation. It does not add detail for form_id or context, so it does not reach 5.

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 opens with a specific verb and resource: 'Delete a node from a form.' It clearly differentiates this from sibling tools like clipform_delete_form and clipform_delete_node_media, and it adds object-level constraints by naming the start node and last end screen as exceptions.

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?

The description gives clear operational context: it explains the re-linking side effect, explicitly states that start nodes and the last end screen cannot be deleted, and notes that user confirmation is required. It does not explicitly compare against alternatives such as clipform_delete_node_media, so it stops short of full when/when-not alternative routing.

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