Query the evidence chain for a vacation rental property or specific booking. Returns independently verified evidence records filtered by property_id, booking_id, or event_type. Use this to audit the complete evidence trail.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 50) | |
| booking_id | No | Booking UUID (optional) | |
| event_type | No | Filter by event type | |
| property_id | No | Property UUID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover safety (readOnlyHint=true, destructiveHint=false). The description adds useful behavioral context: it returns 'independently verified evidence records' and supports filtering by specific IDs or event type. It does not mention pagination or default behavior when no filters are provided, but with annotation coverage, the added context earns a 4.
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 sentences, front-loaded with the primary action. Each sentence earns its place: the first states what it does, the second describes the return and filters, the third states the use case. No filler or redundancy.
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?
With 4 optional params, good annotations, and no output schema, the description covers purpose, return type, filters, and use case. It lacks details about what happens when no filters are provided or how result sets are structured, but for a query tool with high schema coverage, these are minor gaps.
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 coverage is 100%, with each parameter described in the schema. The description mentions the three main filters (property_id, booking_id, event_type) but does not add meaning beyond what the schema provides, such as parameter combinations or output shape. Baseline 3 is appropriate when schema does the heavy lifting.
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 ('Query') with a clear resource ('evidence chain') and scope ('for a vacation rental property or specific booking'). It also states what it returns ('independently verified evidence records') and differentiates from sibling tools by focusing on auditing the complete evidence trail rather than verification or timeline generation.
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?
Provides clear context: 'Use this to audit the complete evidence trail.' This implies when to use it (auditing) and implicitly contrasts with verification tools in the sibling list. However, it does not explicitly name alternatives or state when not to use it, leaving a small gap.
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.
