geometry_nodes_link

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

No annotations beyond destructiveHint=false describe behavior, and the description only states the link action. It does not disclose whether existing socket connections are replaced, what happens if a socket name does not exist, or whether default socket values are used automatically. The description does not contradict the annotations.

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 one front-loaded sentence with no filler or repetition. Every word contributes to the core purpose.

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 no parameter descriptions, no output schema, and semantic details left to defaults, this is under-specified. An agent cannot determine how to identify nodes vs sockets, what to_node='' means, or what response/errors to expect after linking.

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. 'Two nodes' and 'by socket names' only weakly map to from_node/to_node and from_socket/to_socket; node_group_name and the meaning of the optional to_node default are not explained. Parameter names provide some hint, but the description adds little beyond them.

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 states a specific verb (Link), a resource (two nodes in a geometry node group), and the mechanism (by socket names). It is clearly distinct from siblings like shader_link_nodes and other geometry_nodes_* actions.

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 description implies this is the tool for wiring up geometry node groups, but it gives no explicit when-to-use guidance or alternatives. It does not mention prerequisites, such as nodes already existing in the group or socket-name matching, so an agent must infer the usage context.

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