connect_material_expressions

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

No annotations are provided, so the description carries full burden. It explains parameters and special values (e.g., to_node='material'), but does not disclose side effects, permissions, error conditions, or whether connections are idempotent.

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 structured as a docstring with a clear introductory sentence and an 'Args' section. It is concise and informative, though the missing material_path description slightly diminishes its efficiency.

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?

The description covers most parameters but omits the required 'material_path'. With an output schema existing, return values need not be explained, but the description lacks behavioral context and does not fully compensate for absent annotations.

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?

The description adds meaning to from_node, to_node, to_pin, and from_pin by explaining their roles and possible values, which is valuable given 0% schema description coverage. However, it fails to describe the required 'material_path' parameter, leaving a significant gap.

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 clearly states the purpose: 'Connect two expression nodes using their indices.' It specifies the action (connect) and resource (expression nodes), and distinguishes from sibling tools like disconnect_material_expression and connect_blueprint_nodes.

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 provides parameter details but does not explicitly state when to use this tool versus alternatives. It lacks guidance on prerequisites, exclusions, or context for when this tool is appropriate.

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