compositor-link

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

This is a mutation tool (it links sockets, likely creating a connection between nodes) with NO annotations provided, so the description carries full burden for behavioral disclosure. The description is extremely terse ('Link two compositor node sockets') and does not disclose any behavioral details such as: whether existing links are replaced, what happens if the link fails, whether the operation is idempotent, or any side effects. For a mutation operation, this is a significant gap.

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 concise: 'Link two compositor node sockets' in 5 words. It is not verbose nor redundant. However, it is extremely terse, bordering on under-specification. For a tool with 4 parameters and no other information, this brevity comes at the cost of clarity; but as a standalone description it is clear for a simple linking operation.

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 tool has 4 required parameters, no enums, no output schema, and no annotations. The description must carry the full burden to explain what the operation does and any nuances of linking sockets in a compositor. Given the complexity of a node-link operation (potential for invalid connections, type mismatches, etc.), the description is too thin. It does not mention the compositor context, how to specify sockets (name or index), or any error behavior. For an experienced Blender user, this may be sufficient, but the machine-readable description should provide more 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?

Schema description coverage is 0%, so the description must compensate for parameter meaning. The description says nothing about the parameters beyond the schema's titles which already exist in the schema (e.g., 'Destination node name', 'Source output socket name or index'). The parameter names (from_node, from_socket, to_node, to_socket) are fairly self-explanatory, but the description adds no extra meaning about how to construct these values (e.g., how to specify name vs index, what syntax is expected).

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 action ('Link two compositor node sockets'), specifying the verb 'Link' and the resource 'compositor node sockets'. This is specific enough to distinguish from sibling tools like 'shading-link_nodes' (which links shader nodes) and 'compositor-add_node' (which adds nodes), so it differentiates between similar link operations.

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 tool name and description clearly state the action ('Link two compositor node sockets') and the parameter names fully align with the schema. There is no sibling differentiation because the other link tool (shading-link_nodes) exists for a different node type, so the purpose is inherently distinct. However, there are no explicit usage guidelines about when to use this tool versus alternatives, nor any context on prerequisites or use cases.

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