get_service_priceGet full details for a single bookable catalog item by its id (from search_services or browse_service): price, original price, duration, rating, image, and its requirements/inclusions/exclusions/FAQs.
| Name | Required | Description | Default |
|---|---|---|---|
| itemId | Yes | The catalog item's numeric id |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description doesn't need to cover safety. It adds behavioral detail by enumerating the exact output fields (price, original price, duration, rating, image, requirements/inclusions/exclusions/FAQs) and the 'bookable' constraint, which goes beyond the annotations. No 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, front-loaded sentence that begins with the primary action and immediately specifies the target resource. It packs a lot of specific detail (field list, source tools) without any filler or redundancy, earning every word.
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?
Given the simple complexity (1 parameter, no output schema, full schema coverage, and helpful annotations), this description is complete. It explains how to get the item ID, what data will be returned, and the tool's read-only nature via the annotations. There is no missing information for an agent to select and invoke this tool correctly.
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?
The schema already provides a full description for the single parameter itemId ('The catalog item's numeric id'), giving 100% schema coverage. The description reiterates 'by its id' and mentions the source tools, but it doesn't add new semantic meaning beyond what the schema already conveys. Baseline of 3 applies.
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 uses a specific verb ('Get') and names the exact resource (a single bookable catalog item by its id). It lists the specific data fields returned (price, original price, duration, rating, image, requirements/inclusions/exclusions/FAQs), clearly distinguishing this from sibling tools like search_services (which searches lists) and browse_service (which browses categories).
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 states that the id comes from 'search_services or browse_service', establishing a clear workflow and prerequisite for using this tool. However, it doesn't explicitly explain when to use this tool instead of those siblings or mention any exclusions, so guidance is strong but not exhaustive.
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 clearly distinct role: listing top-level categories, drilling into a category, searching across the catalog, fetching item details, and providing the app download link. There is no meaningful overlap between these actions.
All tool names follow a consistent verb_noun pattern in snake_case: browse_service, get_app_download_link, get_service_price, list_service_categories, search_services. This makes the set predictable and easy to navigate.
Five tools is a well-scoped size for a catalog browsing and app-link helper server. Each tool covers a distinct step in the user journey without unnecessary bulk or missing essentials.
The tool set fully covers the pre-booking discovery path: list categories, browse hierarchy, search, inspect details, and hand off to the app. Since actual bookings are explicitly delegated to the app, there are no obvious gaps in the server's intended scope.