connect_geonodes

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the obvious action. It does not explain what happens to existing connections, whether type mismatches are validated, or any side effects that may occur.

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 single sentence is concise, front-loaded, and free of filler. However, it is so terse that it sacrifices useful detail, making it efficient but slightly under-specified.

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 tool with six required parameters, an output schema, and zero schema descriptions or annotations, this description is highly incomplete. It does not clarify how to identify nodes, what the input/output values represent, or any constraints, leaving the agent to guess.

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 must compensate. It does not explain any of the six parameters, though the parameter names (from_node, from_output, to_node, to_input) imply the wiring direction. No details are given about acceptable value formats (e.g., string node IDs vs. integer indices) or required modifier names.

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 identifies the resource as 'nodes in a geometry node tree,' which distinguishes it from shader or compositor node connectors. It conveys the core function effectively, though it could mention the from/to wiring detail to be even clearer.

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?

No guidance is provided on when to use this tool versus connect_shader_nodes or connect_comp_nodes. The description is just a bare statement of functionality with no context on prerequisites, such as requiring an existing geometry node modifier or a valid node tree.

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