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

Description says 'Create', implying mutation, but annotations have readOnlyHint=true, indicating read-only behavior. This is a clear contradiction. No further disclosure of behavioral traits (e.g., side effects, auth needs).

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?

Single sentence with no wasted words, front-loaded with action and resource. Highly concise.

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?

Missing output schema, no return value description, and parameter details are absent. Given 5 parameters (2 required) and sibling tools, the description fails to provide enough context for complete usage.

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%, and description only vaguely mentions 'IDs or slugs' without specifying format, types, or relationships. No added meaning beyond parameter names for park, trail, campground, start_date, end_date.

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?

Description clearly states verb 'Create' and resource 'structured, day-by-day itinerary outline' from 'selected trail/park/campground IDs or slugs'. It distinguishes from siblings like adventure.candidates which likely suggests options, and search/get tools that retrieve raw data.

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?

Description implies usage after selection of IDs/slugs, but does not explicitly state when to use this tool over alternatives like adventure.candidates or individual get tools. No when-not-to-use guidance or prerequisites mentioned.

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