connect_compositor_nodes

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

No annotations exist, so the description must carry the burden of behavioral disclosure. It says nothing about side effects, required state (e.g., compositor must exist), or what happens on execution. The agent has no idea what 'connect_compositor_nodes' does beyond the name.

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 a single short phrase, but it is under-specified rather than appropriately concise. It lacks any substance that would earn its place. No structure or front-loading of useful information.

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 node-connection operation with four required parameters, no annotations, and no output schema documentation, this description is woefully incomplete. It does not explain the return value, node/socket syntax, or any operational requirements. The agent cannot reliably call this tool.

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 schema has 0% description coverage, and the description provides no parameter information. The parameter names are self-explanatory (from_node, from_socket, etc.), but the description adds zero semantics about their types, formats, or relationships. The agent cannot infer how to specify sockets or nodes.

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 exactly the tool name prefixed with 'Blender Studio Pro MCP:', which is a tautology. It restates the name without explaining the action or resource, and fails to differentiate from sibling connect tools like connect_shader_nodes or connect_gn_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?

There is no guidance on when to use this tool versus alternatives like connect_shader_nodes or connect_gn_nodes. No context, prerequisites, or exclusions are provided.

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