Flag a vacation rental booking for enhanced monitoring by lilo's protection system. Creates an alert with the specified reason and risk indicators. Use this when a host identifies concerning behavior. Requires booking_id and reason. Optional: array of risk_indicators.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | Reason for flagging | |
| booking_id | Yes | Booking UUID to flag | |
| risk_indicators | No | Risk indicators observed |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true, so the agent knows it's a mutating operation. The description adds that it 'Creates an alert with the specified reason and risk indicators,' giving context about the side effect. It does not contradict annotations and provides useful behavioral detail beyond the structured metadata.
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 three sentences long, front-loaded with the primary action, and includes usage context and parameter summary without wasted words. Every sentence adds value, making it highly efficient and well-structured.
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 simple mutation tool with no output schema, the description covers the action, purpose, usage trigger, and required parameters. It is sufficiently complete for an agent to correctly select and invoke the tool, matching the completeness of top-tier calibration examples.
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 input schema already provides 100% coverage with descriptions for all parameters. The description restates required vs. optional parameters ('Requires booking_id and reason. Optional: array of risk_indicators') without adding new semantic meaning or examples. This meets the baseline but does not exceed 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 tool's purpose: 'Flag a vacation rental booking for enhanced monitoring by lilo's protection system.' It specifies the resource (vacation rental booking), the action (flag), and the context (protection system), distinguishing it from sibling risk-analysis tools.
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 includes an explicit usage trigger: 'Use this when a host identifies concerning behavior.' This provides clear context for when to invoke the tool, though it does not mention alternatives or exclusions. That would merit a 5, but the guidance is specific enough for a 4.
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 is significant overlap and redundancy among tools, causing ambiguity. For example, analyze_booking_threat_risk, analyze_guest_communication_risk, and analyze_guest_interaction_risk are aliases or near-duplicates, and multiple tools like get_vacation_rental_details and fetch_vacation_rental_details appear to serve the same purpose. This makes it difficult for an agent to choose the correct tool without confusion.
Most tools follow a consistent verb_noun pattern (e.g., check_vacation_rental_availability_and_pricing, get_vacation_rental_details), which aids readability. However, there are minor deviations, such as some tools using 'analyze' vs. 'assess' or 'detect' for similar risk functions, and a few tools like 'ingest_philadelphia_public_records' use a different verb style, but overall the naming is largely predictable.
With 67 tools, the count is excessive for a vacation rental server, leading to bloat and potential overwhelm. Many tools could be consolidated (e.g., multiple risk analysis tools, duplicate property detail fetchers), and the scope feels unfocused, including niche tools like those for Philadelphia events or World Cup compliance that might be better handled as parameters in broader tools.
The tool set provides comprehensive coverage for the vacation rental domain, including booking, risk assessment, compliance, maintenance, evidence management, and guest interactions. There are no obvious gaps; it supports full CRUD/lifecycle operations and specialized workflows, ensuring agents can handle most scenarios without dead ends.
