search_boatsSearch listed boats, optionally filtered by harbor, type, minimum capacity, and max hourly price, with sorting and pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| sort | No | name | |
| type | No | ||
| limit | No | ||
| harbor | No | ||
| maxPrice | No | ||
| minCapacity | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that results support sorting and pagination, which is useful behavioral context, but it does not disclose defaults, maximum page size, or response structure.
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, front-loaded sentence with no filler. Every clause adds meaning: the resource, the optional filters, and the result-shaping behaviors.
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 read-only search tool with seven optional parameters, the description plus schema is minimally viable, but no output schema exists and the description never mentions what a result looks like. An agent can invoke it correctly but would be guessing at the response shape.
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 0%, so the description must compensate. It maps most parameters clearly ('harbor', 'type', 'minimum capacity', 'max hourly price', sorting/pagination), and 'max hourly price' clarifies maxPrice. However, it does not explain enum values, defaults, or constraints beyond what parameter names imply.
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?
States a clear verb and resource, 'Search listed boats', and enumerates the filtering dimensions (harbor, type, min capacity, max hourly price). It does not explicitly contrast with siblings like search_captains or get_boat, but the resource and filter scope make its purpose recognizable.
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 phrase 'optionally filtered' implies this tool is for broad, filtered searches rather than direct lookups, which loosely distinguishes it from get_boat, but it never names alternatives or states when not to use it. Usage context is only implied, not explicit.
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 action or resource: availability checks, bookings (with/without captain), data retrieval for boats/captains/harbors, quotes, and searches. The descriptions clearly differentiate similar tools like create_boat_rental vs. create_booking.
All tool names follow consistent verb_noun snake_case pattern (e.g., check_availability, create_booking, search_boats). No mixing of styles or ambiguous verbs.
10 tools is well-suited for a booking platform covering search, details, quotes, and booking creation. Every tool serves a clear purpose without redundancy.
The core booking workflow (search, check availability, quote, create) is fully covered. Missing tools for viewing existing bookings or cancellations, but these are minor gaps for a public-facing API.