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

Annotations already declare non-read-only, non-idempotent, non-destructive, but the description adds the crucial non-obvious behavior: without confirm=true nothing is cloned and you get back the pipeline/voices/quality gates as a preview, while force=true skips the reuse check. This is exactly the extra context annotations cannot convey.

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?

Purpose is front-loaded, followed by the usage precondition and then the confirm/force behavior. Dense but every sentence earns its place; the parenthetical 'asking for audio is not picking one' is slightly indirect but useful.

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?

With an output schema present, 100% schema coverage, and full annotations, the description covers the one thing an agent could get wrong — that the default call clones nothing and returns a preview. Nothing needed to invoke it correctly is missing.

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 100%, so the baseline is 3. The description still adds the intent behind confirm ('to show them') and force ('skips the reuse check') beyond the schema's terse wording, earning a modest lift.

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 gives a specific verb+resource+scope: 'Clone a template into this workspace as a runnable workflow.' That is clearly distinct from create_workflow / create_workflow_from_intent by virtue of the template source, though no sibling is named explicitly.

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?

'Call only after the user picked THIS template — asking for audio is not picking one' supplies a real precondition and an anti-pattern (asking for audio isn't selection). It stops short of naming the alternative tools (create_workflow_from_intent) an agent should use instead.

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