link_parameters

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'create a channel reference' without explaining side effects, whether existing references are overwritten, if the parameters must already exist, or any required permissions. This is minimal for a mutation tool and leaves significant gaps in understanding the operation's impact.

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, concise sentence that immediately states the purpose. It contains no filler or redundant content, making it efficient and front-loaded.

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 4 parameters, no annotations, no output schema, and no parameter descriptions, the one-sentence description is inadequate to fully understand how to invoke it correctly. The agent is missing crucial information about what paths refer to, what a channel reference is, and any side effects, leaving the description incomplete for a competent use of the 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 input schema has 0% description coverage, and the description names only dst_parm and src_parm, clarifying their directional relationship. However, it does not explain src_path and dst_path at all, and gives no details about the expected format or meaning of these paths. The description adds some meaning about direction but fails to compensate for the lack of schema descriptions for all parameters.

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 (create a channel reference) and the resources involved (dst_parm to src_parm). This is a specific verb+resource construction that distinguishes it from siblings like set_parameter or set_expression, which focus on value assignment or expressions rather than linking.

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. It does not mention prerequisites, when a channel reference is appropriate, or compare with other parameter-related tools such as set_expression. The description simply states the action without providing usage context or exclusions.

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