disconnect_signal

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

Discloses persistence in .tscn, auto-save, return format (plain-text confirmation), and error condition (if connection does not exist). Annotations only provide destructiveHint: true, so description adds substantial behavioral context beyond that.

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?

Three concise sentences with no fluff; front-loaded with main action, then supporting details. Every sentence adds value.

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 (6 required parameters, destructive action, no output schema), the description covers prerequisites, recovery, behavior, error handling, and return format, leaving no major gaps.

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?

All 6 parameters are fully described in the input schema (100% coverage), so the description does not need to add parameter details. It adds no extra meaning beyond the schema, earning a baseline 3.

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?

Clear verb 'Remove an existing signal connection between two nodes' immediately states action and resource. Distinguishes from sibling tools like connect_signal (opposite) and get_node_signals (for confirmation).

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?

Explicitly recommends using get_node_signals first to confirm connection existence and notes recovery requires connect_signal, providing clear when-to-use and when-not-to-use guidance.

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