connect_geometry_nodes

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

No annotations are provided, so the description bears full responsibility for disclosing side effects. It states the operation (connect) but says nothing about whether an existing connection is replaced, whether multiple wires are allowed, whether sockets must be input/output, or what happens on invalid names. This leaves the agent guessing about mutation behavior.

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 compact, with a one-line purpose followed by a clean Args block. It is front-loaded with the core intent and contains no filler. The minimal label expansions are redundant with the schema titles but are still organized and skimmable.

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?

With five required parameters, zero annotations, no output schema, and 0% schema description coverage, the description needs to provide a complete mental model for a correct call. It does not explain prerequisites (existing node group and nodes), exact socket-name/socket-direction requirements, or error/return behavior, so an agent would likely need trial and error.

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%, so the description needed to add real semantics for all five required parameters. It only restates the parameter names with shallow labels ('Source node name', 'Target socket name'), adding almost nothing beyond the schema's own titles. It omits exact name matching rules, socket direction, and value formats.

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 action ('Connect two nodes') and a concrete resource context ('in a geometry node tree'), which distinguishes it from connect_shader_nodes. It does not restate the tool name and names the key objects involved. Minor gap: it doesn't explicitly say it creates a wire from from_socket to to_socket, but the Args section clarifies source/target.

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 'in a geometry node tree' implies a use context and creates implicit contrast with shader-node wiring. However, there is no explicit guidance about prerequisites (nodes already added, valid group) or when to prefer this over add_geometry_node, connect_shader_nodes, or create_procedural_distribution. The sibling tool names make the distinction inferable, but the description itself doesn't spell it out.

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