copy_channel

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

The annotations indicate this is not read-only, and the description adds that all parameters are copied. However, it does not disclose edge cases like source and destination being the same channel or explicitly state that the destination's existing settings are overwritten.

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, direct sentence with no filler. It front-loads the action and identifies the operand immediately.

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 simple tool with two well-described enum parameters and no output schema, this description is largely complete. It could mention overwrite behavior, but that is not essential given the tool's simplicity.

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 covers both parameters with clear descriptions and enumerations, so the description adds little beyond the schema. This matches the baseline for high schema coverage.

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 uses a specific verb ('copy') and identifies the exact resource ('all parameters from one channel to another'). It clearly distinguishes this tool from the surrounding get_/configure_ siblings.

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 clear context: use it to duplicate all parameters between channels. It does not explicitly mention alternatives or when not to use it, but the purpose is self-evident from the sibling tool set.

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