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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that these are catalogue templates rather than live journeys and that instantiation is a separate call, which is useful context but not deep behavioral detail — no mention of return shape or whether the catalogue is fixed vs. user-extensible.

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 tight sentences, examples front-loaded, and the follow-up tool named last. Every clause earns its place with no filler.

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 zero-parameter, read-only list tool with no output schema, the description supplies enough: what the items are, examples of them, and how to act on one. Minor gap is that it doesn't hint at how results are organised or whether all recipes are returned.

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 tool takes no parameters, so there is nothing for the description to disambiguate. Baseline 4 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 states the resource clearly — ready-made journey starting points — and backs it with concrete examples (roadmap voters, unhelpful articles, failed payments, welcome series), which distinguishes it from list_journeys and create_journey. It never uses an explicit verb like 'list', but the name carries that and the content is unambiguous.

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?

It defines the workflow: browse recipes here, then hand one to create_journey_from_recipe to turn it into a draft. That names the natural follow-up tool and the condition for using it. It stops short of saying when NOT to use it (e.g. to inspect existing journeys, use list_journeys).

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