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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, lowering the bar. The description adds two useful facts beyond that: only published activities are searched, and prices are indicative. It omits pagination behavior despite page/page_size params and gives no hint at result ordering or shape.

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, no waste: the search scope and filters come first and the sibling pointer follows. The trailing price caveat is short and earns its place by warning about data quality.

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 and nine optional parameters, the description should say more about what results look like and how pagination works (page max 50, page_size max 20). It covers the filtering surface but leaves the return shape and paging behavior to be discovered by the agent.

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 description coverage is 0%, so the description is expected to carry parameters. It maps most filters (text, destination slug, category slug, adrenaline rating range, months, maximum duration), but page and page_size are never mentioned, and the min/max boundaries on adrenaline are not explained beyond a redundant (1-10) note already in the schema.

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 (Search) and resource (published adrenaline activities on Adrenaline List), plus the filter dimensions it supports. It doesn't explicitly contrast with get_adventure or list_rankings, but the singular-vs-search distinction against siblings is reasonably inferable.

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 list_search_options for valid slugs" is an explicit pointer to a sibling tool and a prerequisite for correct slug values. It stops short of saying when to prefer get_adventure or list_rankings, so there is no true when-not-to-use guidance.

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