get_traveler_context

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context: requires a Gondola API key, returns formatted travel context or instructions to build one, and lists the types of data returned (loyalty programs, home airport, etc.). No contradiction with annotations.

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 front-loaded with the core purpose in the first sentence. It then adds behavioral and usage details. While it has three paragraphs, each sentence adds meaningful information. Slightly longer than minimal but still efficient.

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?

Given no parameters and the presence of an output schema (likely detailed), the description covers prerequisites (API key), usage timing, and return content. It is complete for this tool's simplicity and context.

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?

There are no parameters (0 params, 100% schema coverage), so baseline is 4. The description adds value by detailing what the tool returns, which is beyond the schema's scope (schema only says 'object'). No further parameter information needed.

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 'Get the user's saved travel context to personalize recommendations.' It uses a specific verb ('Get') and resource ('travel context'). It distinguishes from siblings by positioning itself as 'the single best source of who this traveler is' and advising to call it first.

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 explicitly says to 'Call this once at the start of a travel or planning session and weigh it across hotel, flight, and car recommendations.' This gives clear context for when to use it, though it does not explicitly list alternatives or when not to use it.

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