cm_copy_journey

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

No annotations beyond title. The description says 'Copy' but doesn't disclose whether the original journey is affected, what fields are copied, whether it returns the new journey ID, or any side effects. Annotations provide no safety hints.

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 sentence that conveys the core purpose. It is concise and front-loaded, but could benefit from a second sentence about usage or return value.

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?

No output schema is present, and the description does not explain what the tool returns (e.g., new journey ID, success status). Given the complexity of copying a journey (likely multiple steps), the description is insufficient for an agent to fully understand the behavior.

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 each parameter has a description. The tool description does not add any extra meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the action (copy) and resource (journey) and specifies the destination (client and list). It distinguishes from sibling tools like cm_get_journey or cm_create_journey (though the latter isn't in siblings). However, it could be more precise about whether it copies the entire journey or just structure.

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?

No guidance on when to use this tool versus alternatives (e.g., cm_create_journey, cm_copy_template). No mention of prerequisites or scenarios where copying is appropriate.

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