browse_serviceGiven a service category id (from list_service_categories), return what's inside it: either bookable catalog items with prices and images directly, or its sub-categories (drill in again with the sub-category's catalog) — mirrors how the Fixidu app itself branches.
| Name | Required | Description | Default |
|---|---|---|---|
| serviceId | Yes | A service category id from list_service_categories |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as read-only, open-world, and idempotent. The description adds valuable behavioral context beyond those hints: the output is heterogeneous (either direct items or sub-categories) and recursive drilling is expected. This helps the agent anticipate response shape and plan subsequent calls.
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, well-structured sentence that front-loads the core action, then efficiently explains the two possible output types and the recursive pattern. Every clause contributes meaningful information, and there is no padding.
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?
Without an output schema, the description does a good job of setting expectations for the response: either items with pricing/images or sub-categories to drill into. It omits edge-case details (e.g., invalid IDs, pagination), but for a browse tool with one parameter and clear branch behavior, it is essentially 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?
The schema already fully describes the sole parameter serviceId as 'A service category id from list_service_categories' with 100% coverage. The description repeats this information without adding new semantics, so it meets the baseline for high coverage but does not elevate beyond it.
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 action: given a service category id, return what's inside it (either bookable catalog items with prices/images or sub-categories). It explicitly distinguishes from sibling tools by describing the drill-down behavior that mirrors the Fixidu app, making it more specific than a generic 'browse'.
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 context: you must first use list_service_categories to obtain a serviceId, and you can drill into sub-categories recursively. It does not explicitly state when NOT to use this versus search_services or get_service_price, but the input contract and branching behavior provide clear enough 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.
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.