get_past_trips

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

Discloses need for API key, returns summary with dates/numbers/costs/loyalty, explains limit behavior (most recent first, response notes existence of more). Annotations already declare readOnlyHint=true and no destruction; description adds useful context beyond 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?

Concise three paragraphs: purpose, summary of returns, parameter details. Front-loaded with primary action. Every sentence adds value without redundancy.

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 one simple parameter, comprehensive annotations, and output schema (implied by 'Returns formatted list'), the description covers account requirement, parameter behavior, and return value expectations. Fully sufficient for correct tool selection and invocation.

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 has one parameter 'limit' with no description in schema (0% coverage). Description fully compensates: explains that limit controls count, default 20, most recent first, and that the response indicates if more exist, guiding agent to raise limit only when full history is 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?

Clearly states 'Get the user's past trips including hotel stays and flights.' The verb 'Get' and specific resource 'past trips' with included types distinguish it from siblings like 'get_upcoming_trips'.

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?

Implies when to use: when user wants past travel history. Mentions requirement of Gondola account. Does not explicitly contrast with alternatives like 'get_upcoming_trips' or provide when-not-to-use guidance, which would be ideal.

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