connect_signal

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

With no annotations, the description must carry the behavioral burden. It does disclose a key side effect—persistence into the scene file—which is more than a purely abstract statement. However, it does not mention what happens on duplicate connections, whether existing connections are replaced, whether the scene must be open/saved, or validation behavior for invalid paths/signals.

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 front-loaded sentence of eleven words with no filler. Every word contributes meaning and it is immediately scannable, making it highly concise and well-structured.

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?

Despite clear purpose, this is a mutation tool with no annotations, no output schema, no description of return values, error conditions, or prerequisites. For an operation that writes to scene files, the description leaves significant gaps about invocation context and expected outcomes.

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 description coverage is 0%, and the description does not explain the parameters beyond the high-level mapping of 'node signal' and 'target node.' Parameter names are suggestive but lack needed format details, such as whether paths are scene-relative or absolute, and whether nodes/signals must already exist in the scene.

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 uses a specific verb ('Connect') and clearly names the resource (a node signal) and the outcome (method on a target node, persisted into the scene file). The persistence detail distinguishes it from runtime signal watching tools like watch_signals and from the inverse disconnect_signal sibling.

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 phrase 'persisted into the scene file' implies this is for making static, scene-saved connections rather than runtime-only ones, but there is no explicit when-to-use or when-not-to-use guidance, nor mention of alternatives like watch_signals or find_signal_connections.

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