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

Annotations already declare readOnlyHint, destructiveHint=false, and idempotentHint, so the safety profile is covered. The description adds value beyond that by disclosing what comes back — live vs. draft status and per-journey email send counts — which is useful since there is no output schema.

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?

It is a single dense sentence plus a short imperative, with the definition front-loaded before the usage rule. The parenthetical trigger examples (segment join, form submission, paid order) are the only slightly expendable part, but they earn their place as domain illustration.

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 no output schema, the description correctly spends its words on what is returned (status, send counts) and when to call it. It leaves out list mechanics such as pagination, ordering, or result limits, which an agent may need at scale.

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%, so both site_id and user_goal are fully documented in the schema itself. The description adds no syntax, format, or scoping detail beyond the implicit 'the site's' framing, which is the expected baseline when the schema does the work.

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?

It names the resource (the site's automation journeys) and defines it concretely as multi-step sequences triggered by events, which is genuinely clarifying domain vocabulary. It stops short of distinguishing this list from the single-record sibling get_journey, so an agent must infer that this returns the collection rather than one journey.

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 sentence 'Call it before draft_journey so you do not duplicate one' gives an explicit ordering and rationale for choosing this tool first. It offers no exclusion guidance (e.g., when to use get_journey instead), but the pre-flight use case is clearly spelled out.

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