Get the available session difficulty levels for a surf pool (e.g. Beginner, Intermediate, Advanced). Use the level names with find_sessions.
| Name | Required | Description | Default |
|---|---|---|---|
| pool_id | Yes | Pool ID — use list_pools to get valid values |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. The verb 'Get' implies a safe, read-only operation, and the examples clarify the return content. However, it does not disclose potential behaviors such as error handling, authentication requirements, or whether the tool can fail for invalid pool IDs. This is adequate for a simple lookup but not fully transparent.
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 concise, consisting of two sentences. The first sentence states the tool's purpose with examples, and the second gives actionable guidance for using the output. No unnecessary words or repetition; it is well-structured and front-loaded.
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 tool with one parameter and no output schema, the description is complete. It explains what is returned (difficulty levels with examples) and how to use the result with find_sessions. The parameter description also points to list_pools for valid inputs, covering the full workflow. 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?
Schema description coverage is 100%, with the pool_id parameter already documented as 'use list_pools to get valid values'. The description adds no further parameter-level detail, so the baseline of 3 applies. It does not introduce format, syntax, or additional constraints 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's purpose with a specific verb ('Get') and resource ('available session difficulty levels for a surf pool'), and provides concrete examples (Beginner, Intermediate, Advanced). It distinguishes itself from sibling tools by tying the output to 'find_sessions', making its unique role evident.
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 instructs to 'Use the level names with find_sessions', giving clear downstream usage. It also indirectly references 'list_pools' via the parameter description for obtaining a valid pool_id. While it lacks explicit 'when-not-to-use' caveats, the guidance for this simple getter is strong and unambiguous.
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 has a clear, distinct purpose: list_pools retrieves pools, get_session_levels provides difficulty levels for a pool, and find_sessions returns available sessions. There is no functional overlap between them.
All tool names follow a consistent verb_noun pattern in snake_case (list_pools, get_session_levels, find_sessions), making them predictable and easy to use.
Three tools are appropriate for the scope of finding surf sessions: discover pools, get levels, and search sessions. The count feels lean but complete.
The tool set covers the essential workflow: listing pools, retrieving levels, and searching sessions. The booking URL in find_sessions externalizes booking, which is reasonable. A minor gap is the lack of a tool to fetch detailed info for a specific session, but it's not critical.
