Create a Wanderlog trip

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: the trip is created empty with pre-generated day sections, returns a trip key for reference, and provides practical guidance about what makes a good itinerary. It doesn't mention error conditions or rate limits, but covers the essential creation workflow thoroughly.

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?

The description is appropriately sized and front-loaded with the core purpose in the first sentence. The subsequent guidance about populating the trip is valuable but somewhat lengthy. Every sentence serves a purpose, though some could be more concise. The structure flows logically from creation to population guidance.

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 creation tool with no annotations and no output schema, the description provides excellent contextual completeness. It explains the creation outcome (empty trip with day sections), the return value (trip key), and comprehensive guidance on how to use sibling tools to build a complete itinerary. This addresses the complexity of trip creation in Wanderlog's ecosystem effectively.

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?

With 100% schema description coverage, the baseline is 3. The description doesn't add any parameter-specific information beyond what's already documented in the schema descriptions. It mentions 'destination and date range' generically but provides no additional syntax, format, or usage details about the parameters.

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 clearly states the specific action ('Creates a new Wanderlog trip') with precise resource details ('for the given destination and date range') and distinguishes it from siblings by explaining it creates an empty trip with pre-generated day sections, unlike other tools that add content. The first sentence provides a complete purpose statement.

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 description provides explicit guidance on when to use this tool (to create a new empty trip) and when to use alternatives, listing four specific sibling tools (wanderlog_add_place, wanderlog_add_note, wanderlog_add_hotel, wanderlog_add_checklist) that should be used together after creation to populate the trip. It also explains the relationship between tools for creating a complete itinerary.

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