discord_clone_channel

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

Annotations provide readOnlyHint=false and destructiveHint=false, indicating mutation but not destruction. The description adds context: it clones including name, topic, and overwrites but not messages, and returns only the cloned channel's name and ID. This goes beyond annotations by specifying scope and return value, though it does not mention side effects like rate limits.

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 three concise sentences: action and scope, permission requirement, return value. It is front-loaded with the primary purpose and contains no redundant 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?

Given 2 parameters, no output schema, and annotations present, the description adequately covers the tool's purpose, included/excluded elements, permission, and return. It is missing details about channel type handling or error cases, but for a simple clone tool it is fairly complete.

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 coverage is 100% for 2 parameters, but the description adds value: it explains that new_name defaults to the source channel's name, which is not in the schema. This provides additional meaning beyond the schema's descriptions.

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 states a specific verb ('Create a copy') and resource ('channel'), and clarifies exactly what is included (name, topic, permissions) and excluded (messages). This differentiates it clearly from sibling tools like discord_create_channel or discord_edit_channel.

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 includes a prerequisite ('Requires the Manage Channels permission') but does not explicitly state when to use this tool versus alternatives like creating a new channel or editing an existing one. The guidance is implicit enough to deduce usage but lacks explicit exclusion criteria.

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