Pricing statistics (count, avg, median, p25, p75, min, max) for a boat category, with optional region (province, country or city) and length range. Prices always match the requested scope; price_scope states whether they are provincial, per country, per place or national.
| Name | Required | Description | Default |
|---|---|---|---|
| regio | No | ||
| type_boot | Yes | ||
| lengte_max | No | ||
| lengte_min | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the tool read-only and non-destructive, so the description needs less safety disclosure. It adds meaningful behavioral context by stating that prices always match the requested scope and that `price_scope` indicates whether results are provincial, national, per place, or per country. This goes beyond what annotations alone provide.
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?
Two concise sentences with no filler. The main purpose is front-loaded, followed by key behavioral detail about price_scope. Every sentence contributes useful information.
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?
The description provides the key input dimensions, the statistic types, and behavioral scope semantics. Even without an output schema, an agent can understand what will be returned and how filtering works. Minor gaps remain around value formats and length units, but they do not prevent correct 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 description coverage is 0%, so the description carries the burden of explaining parameters. It maps 'boat category' to type_boot, 'region (province, country or city)' to regio, and 'length range' to lengte_min/lengte_max. It adds meaning beyond the raw schema, although exact formats and units are not specified.
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 clearly that the tool returns pricing statistics (count, avg, median, p25, p75, min, max) for a boat category with optional region and length filters. It does not explicitly differentiate from siblings like get_market_stats or market_snapshot, but its metric list makes the purpose reasonably distinct.
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 retrieving aggregated pricing stats for a boat category, optionally filtered by region or length. It does not explicitly state when to prefer this over siblings such as get_market_stats or compare_brands, so guidance is mostly implied rather than 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.
Most tools target distinct resources, but get_boat_pricing_stats and get_market_stats overlap heavily: both return count, average, median, min/max price scoped by category and region. ask_bo and get_facts also both return cited factual content, leaving some ambiguity even if the descriptions help.
The set predominantly follows a verb_noun pattern: search_boats, search_rentals, get_brand_info, compare_brands, and get_boat_details all fit cleanly. market_snapshot breaks the pattern as a bare noun phrase, and ask_bo uses a proper noun, but these are minor deviations within an otherwise predictable convention.
11 tools is well-scoped for a multifaceted read-only marketplace domain covering listings, rentals, brands, marinas, knowledge-graph facts, and market statistics. Each tool earns its place, even though a couple of them partially overlap.
Core workflows are covered: boat search and details, rental search, brand lookup and comparison, marina discovery, knowledge-graph facts, and multiple market statistics views. Minor gaps exist, such as no dedicated marina detail endpoint and rental details only appearing via search results, but agents can work around these.
