get_travel_profiles

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

Annotations already declare the operation read-only and non-destructive. The description adds useful behavioral context beyond that: it requires an API key, returns a 'Formatted list of travel profiles with IDs,' and may return 'instructions to add one' when no profiles exist. This is meaningful operational transparency with no contradiction of the 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 short and front-loads the core purpose, but the second sentence is convoluted and repeats 'guest name, email, and phone' and 'prefill' unnecessarily. It conveys useful context but could be tighter without losing meaning.

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 zero-parameter, read-only tool with an output schema, the description covers everything an agent needs: what the tool returns, what profiles are for, and the API key requirement. Nothing essential is missing.

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?

The tool has zero parameters, so the baseline for this dimension is 4. There is nothing for the description to add about parameter meanings; the schema correctly shows an empty properties object.

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 states a specific verb and resource: 'Get the user's saved travel profiles' and clarifies what those profiles contain (guest name, email, phone presets, Profile ID). It clearly distinguishes this from collecting checkout details field by field and, in context, from sibling tools like get_loyalty_accounts or get_traveler_context.

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 implies the usage scenario: profiles exist to prefill guest details at checkout 'instead of collecting name, email, and phone field by field.' It also states a prerequisite, 'Requires a Gondola account (API key).' However, it does not explicitly compare this tool to alternatives or state when not to use it, so usage guidance remains mostly implied.

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