find_surf_trip_guidesUse this when the user wants surf trip planning guidance, such as landlocked surfer planning, where to surf next, avoiding flat trips, cheap surf flights, or Surfline alternatives.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Optional free-form user query to match against guide titles and keywords. | |
| intent | No | The surf trip planning intent. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and non-destructive behavior. The description adds that the tool matches user queries and intents against guide titles and keywords, providing transparency beyond annotations without contradiction.
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, well-structured sentence that lists concrete examples. Every part is useful, with no wasted words.
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 search tool with few parameters and no output schema, the description is complete enough. It covers usage context and behavioral intent, though a brief comparison to sibling tools would enhance completeness.
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?
Both parameters are fully described in the schema with 100% coverage. The description reiterates the examples from the intent enum but does not add new semantic meaning beyond what the schema provides.
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 tool is for surf trip planning guidance and lists specific use cases like landlocked surfer planning and cheap flights. However, it does not explicitly distinguish this tool from siblings like recommend_surf_trip_destinations, which may lead to confusion.
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 contexts for use (e.g., landlocked surfer, where to surf next) and includes a list of intents. It lacks guidance on when not to use the tool or how it differs from similar sibling tools, but the intent enum helps specify usage.
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.
Several tools have overlapping purposes: compare_surf_destinations, recommend_surf_trip_destinations, and find_surf_trip_guides all provide destination recommendations and planning guidance, making it unclear when to use which. The descriptions partially differentiate them but boundaries remain ambiguous.
All tool names follow a verb_noun pattern (e.g., compare_surf_destinations, get_live_spot_forecast) using snake_case. While verbs vary, the pattern is consistent and predictable. No mixing of conventions or unclear naming.
With 5 tools covering recommendations, comparisons, forecasts, and spot details, the count is well-scoped for a specialized surf trip planner. Each tool serves a clear role without being excessive or sparse.
The tool set covers core surf trip planning needs: destination recommendations, comparisons, live forecasts, and spot context. Minor gaps exist (e.g., no tool for managing user preferences or historical data), but agents can still plan effectively.