list_roomsListet alle aktiven Räume des Orbit mit Kapazität, Etage, Ausstattung und Standardpreisen pro Slot (vormittag 08:00–12:00, nachmittag 13:00–18:00, ganztags 08:00–18:00). Räume mit bookableFrom in der Zukunft sind sichtbar, aber noch nicht buchbar.
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | Optional: Kategorie-Slug zum Filtern (siehe `category.slug` im Ergebnis) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that future rooms are visible but not bookable, and lists the returned attributes. While it does not explicitly state read-only nature, the context clearly indicates a non-destructive operation.
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 that are front-loaded with purpose and packed with relevant details. No unnecessary words, and the second sentence adds an important behavioral nuance.
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 no output schema, the description sufficiently explains the return content (capacity, floor, equipment, standard prices per time slot) and covers behavioral context (future rooms visibility). No critical gaps for a listing tool with one optional parameter.
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 only parameter (category) is fully documented in the schema. The description does not add extra meaning beyond what the schema already provides. With 100% schema coverage, baseline of 3 is appropriate.
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?
Title 'Räume auflisten' and description explicitly state listing active rooms with specific attributes (capacity, floor, equipment, standard prices per slot). Clearly distinguishes from sibling tools like check_availability or create_booking by focusing on room listing and static data.
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?
Description implicitly advises using this tool to obtain room details before booking, and highlights that rooms with future bookableFrom are visible but not yet bookable. However, it lacks explicit instructions on when to use this tool versus alternatives like check_availability.
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 purpose: checking availability, listing rooms, listing services, quoting, creating binding bookings, and requesting non-binding bookings. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_availability, list_rooms), making them predictable.
With 6 tools, the set is well-scoped for a room booking system—enough to cover key operations without being excessive.
Covers all major booking creation steps (list, check, quote, book), but lacks tools for updating or canceling existing bookings, which is a minor gap.