connect_signal

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

Discloses persistence in .tscn, auto-save, return value format, and error conditions. No annotations provided, so description carries full burden. Lacks details on permissions or side effects but covers key behaviors well.

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?

Single paragraph with logical flow: purpose, usage guide, behavior, errors. Efficient though slightly dense; no wasted words.

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?

All parameters described, return value explained, error conditions mentioned. No output schema needed. Covers essential context for a 6-parameter mutation tool.

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 100% with descriptions. Description adds workflow context (e.g., signal name examples and check before connecting) that enhances understanding beyond 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?

Description clearly states 'Connect a signal on a source node to a method on a target node, persisting the connection'. Verb+resource is specific and distinguishes from 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?

Explicitly advises to 'Use after get_node_signals to confirm the signal name on the source and the method name on the target' and warns about duplicate connections, providing clear context.

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