trigger_journey_batch

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

Annotations declare destructiveHint=true, and the description usefully adds an explicit confirmation requirement plus a pre-flight sample validation, which is exactly the kind of behavioral caution a bulk mutation needs. It does not, however, describe partial-failure or rollback behavior.

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, roughly twenty words, front-loaded with the action and scope followed by the safety guidance. No filler and nothing redundant.

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 destructive bulk-write tool with no output schema and zero schema description coverage, the confirmation/validation guidance is valuable, but the unexplained journey_id and trigger_name parameters leave gaps an agent must guess at.

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 0% and the description only echoes the recipient limit already enforced by maxItems: 100. Neither journey_id nor trigger_name is explained, so the description does not compensate for the empty schema documentation.

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 (bulk-enroll), the resource (recipients), the target (WhatsApp journey) and a hard limit (up to 100). The 'bulk' framing distinguishes it from the single-recipient sibling trigger_journey, 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?

Implies a workflow — confirm explicitly, validate a sample first — which points toward validate_journey_trigger, but never names the alternative or states the condition for choosing it. Usage context is implied rather than spelled out.

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