link_geometry_nodes

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

No annotations are provided, and the description gives no information about side effects, prerequisites, or outcomes. It does not state that a connection is created between two specific sockets, nor any error conditions.

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 extremely short, which is concise, but it is under-specified to the point of being unhelpful. It is a phrase rather than a meaningful sentence, failing to convey necessary details.

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 has five required parameters and no schema descriptions or output schema, the one-line description is wholly inadequate to understand the tool's function, parameters, or expected behavior in context.

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?

All five parameters (from_node, to_node, from_socket, to_socket, node_group) are entirely undocumented in both the schema and description, achieving 0% coverage. The description adds no explanation of their meaning or roles.

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 is a single phrase '几何节点连线' (Geometry node connection) without specifying the action of linking two sockets or the resource being modified. It is ambiguous between a noun and verb and does not clarify what is being connected.

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?

There is no guidance on when to use this tool versus alternatives like unlink_geometry_nodes or build_geometry_node_tree. The description provides no context for selection.

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