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

Annotations already cover safety (readOnly=false, destructive=false, idempotent=false, openWorld=false). The description adds real context on top: the exact scope of what is replicated, the Discord/Slack/WordPress exclusion, and the required `channels:write` permission. It could still say whether the original is untouched and what the new channel's initial state is.

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?

Three short sentences, front-loaded with the verb and immediate effect, then scope, then permissions. Only mild redundancy between the title echo and the opening line.

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 one-parameter, no-output-schema copy operation, the essentials are present: what is copied, what is deliberately not copied, and the permission required. Return shape and how the copy is identified are left implicit, but not blocking.

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?

Context signals report 0% schema description coverage at the parameter level, and the description contributes nothing about `request`, `id`, `name`, or `key` — notably not the timestamp/'copy' defaulting behavior. The nested schema does document those fields, so the gap is narrow but the description does not compensate for the low coverage signal as required.

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?

States a specific verb (duplicate/copy) and resource (channel), and immediately defines the copy semantics: 'in its project, with every setting, policy, rule and wordlist'. That is enough to separate it from channels-create and channels-update without opening a schema.

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 implies usage (copy rather than build from scratch) and gives one useful exclusion — integrations are not copied — which the agent needs before choosing this over channels-create. But it never names channels-create or states when NOT to duplicate, so routing is left partly to inference.

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