get_outfitterPublic profile of one outfitter: territory, species, season, and up to 8 summarised packages. Rates appear only when the outfitter has confirmed its listing. No phone, e-mail or website is ever returned.
| Name | Required | Description | Default |
|---|---|---|---|
| locale | No | ||
| api_key | No | ||
| outfitter_id | Yes | Outfitter id (e.g. 'PV-0009') or the id-bearing URL segment. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds meaningful behavioral context: rates appear only if the listing is confirmed, and contact info is never returned, plus a cap of 8 packages. This goes beyond the annotations and helps an agent set expectations.
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?
Three short sentences with no filler. The purpose is front-loaded in the first sentence, and behavioral notes follow. Every clause 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 read-only profile tool with no output schema, the description covers the key content (packages, rates condition, contact exclusion) and the fact it's a single record. The main gap is the unexplained locale and api_key parameters, but the tool's simplicity and the annotations covering safety make it mostly complete.
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 only 33% (only outfitter_id has a description). The tool description adds no explanation of the locale or api_key parameters—it doesn't mention them at all. With low schema coverage, the description should compensate but doesn't, leaving the agent without guidance on these parameters.
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 states a specific resource (one outfitter's public profile) and enumerates its content (territory, species, season, up to 8 packages). The phrase 'public profile of one outfitter' clearly differentiates this from siblings like search_outfitters (which finds multiple) and fetch (generic read). It also notes conditional rates, adding precision.
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 usage when you have a single outfitter ID and want its profile, but it does not explicitly mention alternatives like search_outfitters or say when not to use this tool. No exclusions are given, so it only provides implied context without routing guidance.
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.
There are overlapping pairs: search vs search_outfitters, fetch vs get_outfitter, and check_availability vs get_booking_options all cover adjacent territory. The descriptions clearly differentiate each pair's intended use, so an agent can disambiguate, but the boundaries are not immediately obvious.
Most tools follow a verb_noun pattern like get_outfitter and create_price_request, but 'fetch' and 'search' are bare verbs that break the pattern. Also 'search' and 'search_outfitters' are inconsistently named. The style is readable but mixed.
8 tools is well-scoped for a Canadian outfitter discovery and enquiry platform. Each tool covers a distinct step: reference data, search/filter, profile retrieval, availability, booking options, and price requests without unnecessary bloat.
The tool surface covers the full traveller workflow: get valid filter values, search with free text or advanced filters, retrieve full profiles, check availability, get booking options, and send a price request. There are no obvious dead ends; price request management is external via email, so no missing lifecycle operations are needed.