geometry_nodes.connect

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

Annotations include readOnlyHint=false and destructiveHint=false, but the description does not add behavioral context beyond stating 'Risk: standard; maturity: L3'. It does not disclose what happens on connection, whether it modifies the scene, or any side effects. With no annotation contradiction, but given that the description carries the burden for behavioral traits, this is severely lacking.

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 very short and avoids verbosity, but it is under-specified. It includes generic template text ('Risk: standard; maturity: L3') that does not add value. It is technically concise, but conciseness is not useful without substance.

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 tool's complexity (9 parameters, 6 required, 33% schema coverage), the description is grossly inadequate. It does not explain how to use the tool, what the parameters represent, or what the output schema contains. An agent would have no idea how to construct a valid call or interpret results.

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 only 33%, meaning most parameters have no descriptions. The tool description does not explain any of the required parameters (fromNode, fromSocket, toNode, toSocket, groupName). Since the schema is the only source and it is sparse, the description fails to compensate. Parameters like fromSocket/toSocket are ambiguous without context.

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 identifies the command as 'geometry_nodes.connect' but does not explain what connecting does (e.g., linking nodes in a geometry node graph). It lacks a verb that describes the action beyond the name itself. The sibling tool 'blender_geometry_nodes_add_node' suggests graph editing, but the purpose is not clarified.

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 alternatives. While siblings like 'blender_geometry_nodes_add_node' exist, the description does not mention any alternative or condition. The only context is 'Per-request argument checks...', which is not usage guidance.

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