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

Annotations establish this as a non-read-only, non-idempotent, non-destructive write, and the description adds real behavioral detail beyond that: the result is a draft, email steps arrive as draft emails built from templates with recipe copy, and each must be marked ready before publishing. What it doesn't cover is whether repeated calls create duplicate journeys (idempotency implications) or what is returned.

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?

Two sentences, zero filler. The core action is front-loaded and the follow-up caveat about draft emails is the only additional information offered, which is genuinely 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?

For a two-parameter creation tool with full schema coverage and no output schema, the description covers what is created and the post-creation obligation. Only the return value (e.g. new journey id) is left unstated, which is a minor gap.

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% and both parameters already carry descriptions pointing to list_journey_recipes and list_products. The description adds no format or sourcing detail beyond the schema, so the baseline 3 applies.

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 and resource: "Copies a recipe into a new draft journey," which distinguishes it from the sibling create_journey (blank journey) and generate_journey. It doesn't explicitly name those siblings, so an agent must infer the difference from the "from a recipe" framing.

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?

Usage is implied through the required recipe id (the schema points to list_journey_recipes) and the "draft journey" outcome, but there is no explicit statement of when to pick this over create_journey or generate_journey, and no prerequisites or exclusions are named.

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