trigger_customer_journey

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

With no annotations provided, the description fully discloses side effects (immediate email sending), authentication (API key), rate limits (max 10 concurrent), read-only/dry-run mode behavior, and error conditions. This exceeds the burden needed for transparency.

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 well-structured but slightly verbose; however, every sentence adds value and it front-loads the main action. A minor condensing would earn a 5.

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 no annotations, 3 parameters, and a described output schema, the description covers purpose, usage, behavior, parameters, and return values completely, including error handling and return format.

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?

The input schema provides zero parameter descriptions, but the description adds rich semantics: journey_id source, step_id requirement, email_address subscription state. This fully compensates for the 0% schema coverage.

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 tool triggers a contact into a specific step of a Customer Journey workflow, with a specific verb and resource. It distinguishes from sibling tools like start_automation and send_campaign by naming explicit alternatives for other automation types.

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 explicitly states when to use this tool (for Customer Journey workflows) and when not to (for Classic Automations or one-time emails). It also provides prerequisites (contact must be subscribed) and a method to find journey IDs (list_automations).

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