compositor.link

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

With no annotations present, the description carries full responsibility for behavioral disclosure. It only says 'link' without indicating whether linking is additive, destructive, reversible, or whether existing connections are replaced. Critical behavioral traits are missing.

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, efficient sentence with no redundancy. However, its extreme brevity comes at the cost of substance, making it less helpful than a slightly longer description with key 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 complexity of a compositor node linking operation with four required parameters and no output schema or annotations, a one-sentence description is insufficient. It does not explain the linking behavior, socket types, or prerequisites, leaving gaps for an AI agent.

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. However, it adds no detail about the four required parameters (from_node, from_socket, to_node, to_socket). The schema titles provide minimal hints, but the description fails to explain how to use these parameters effectively.

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 verb and resource: 'Link two compositor node sockets'. It conveys the core action and target, distinguishing it from unrelated tools. However, it does not differentiate from similar linking tools in other domains like shading.link_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?

No guidance is provided on when to use this tool versus alternatives such as compositor.add_node or shading.link_nodes. The sibling list includes multiple linking-related tools, but the description offers no conditions or exclusions.

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