Browse current award travel deals and flight promotions.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of deals to return (default 12) | |
| category | No | Optional deal type filter (e.g. 'flight', 'hotel', 'card') |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Browse' is consistent with those. The description adds only minor context ('current', 'award travel deals', 'flight promotions') but does not disclose ordering, freshness, pagination, or what a result entry looks like.
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 a single sentence, front-loaded with the action and resource, and contains no filler or redundant explanation. Every word earns its place.
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 simple read-only listing tool with two optional parameters, the description plus schema is largely sufficient. There is no output schema and no detail about returned fields or ordering, but the low complexity and read-only annotations keep this from being a significant gap.
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 100%, so both parameters are already documented in the schema. The tool description adds no additional meaning for 'limit' or 'category', so the baseline score of 3 is appropriate.
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 uses a specific verb ('Browse') and a concrete resource ('current award travel deals and flight promotions'), and the title 'Browse Award Deals' reinforces the purpose. It does not explicitly contrast with sibling tools like search_flights or search_calendar, so some ambiguity remains about where 'deals' ends and flight search begins.
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 tool is for browsing current deals and promotions, which provides some context for when to use it. However, it gives no explicit when-to-use guidance and does not name or exclude sibling tools such as search_flights or get_prediction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct decision point—searching routes, browsing deals, finding flexible dates, predicting fares, and comparing points value. Search_calendar and search_flights are similar, but descriptions clarify date-flexible versus specific-date/route search.
All tool names follow a consistent lowercase snake_case verb_noun pattern: get_prediction, list_deals, optimize_points, search_calendar, search_flights. There is no mixing of conventions or vague verbs.
Five tools is a well-scoped size for a travel deals and points optimization assistant. Each tool earns its place and none feel redundant or unnecessary.
The set covers the core travel decision workflow: searching flights, viewing flexible dates, browsing deals, predicting fare movements, and optimizing points redemption. A fare alert or booking tool is absent, but those are beyond the apparent decision-support scope.
