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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: results are paginated cards identical in shape to find_journey output, accompanied by a total and a next_offset for continuation. Missing only details like ordering or empty-result 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 tight sentences with the usage trigger front-loaded, followed by the return-shape contract. No filler, no repetition of the title, and every clause carries information the agent needs.

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 still specifies what comes back (a page of journey cards, a total, a next_offset), and the optional category path is fully explained. Nothing required to call or continue pagination correctly is absent.

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 limit, offset and category are all documented with ranges, defaults and the next_offset chaining rule. The description reinforces only the category-to-list_journey_categories relationship and says nothing about limit or offset, so it adds little beyond the schema baseline.

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 and resource ('look through the journeys') with an explicit scope modifier (optionally one category), and contrasts it with the search-oriented sibling find_journey and the source of category slugs, list_journey_categories. An agent can distinguish this browse/list tool from the other eight siblings without opening any schema.

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?

'Use when the user wants to look through the journeys' gives a clear trigger condition, and the parenthetical explains the one optional filter and where its values come from. It does not state an explicit when-not or name the exact condition that would select find_journey instead, so it falls short of full routing guidance.

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