Rezdy Agent MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not clarify that this is a safe, non-destructive read operation (unlike create/cancel siblings), whether quotes expire, or what the response structure contains (e.g., total price, breakdown, validity period).

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?

Extremely concise single sentence with no redundancy. However, for a tool with 8 parameters including nested objects (quantities array, customer object), this brevity is insufficient—the description is front-loaded but too short to support the complexity.

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?

Inadequate for the tool's complexity. With 8 parameters, nested structures, no output schema, and no annotations, the description should explain the quote workflow, parameter interdependencies (e.g., sessionId vs startTime), and the expected response. It currently provides only a label.

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?

With 100% schema description coverage, the structured data already documents all parameters. The description mentions 'pricing details' which loosely maps to the quantities/customer data needed for calculation, but adds no specific syntax guidance, example formats, or relationships between parameters (e.g., sessionId vs startTime). Baseline 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?

States the basic action ('Get a quote') and resource ('booking'), and mentions 'pricing details' as the output focus. However, it fails to distinguish this from the sibling 'rezdy_agent_create_booking' tool—critical context since both likely accept similar parameters but have fundamentally different effects (pricing check vs. actual reservation).

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 no guidance on when to use this tool versus alternatives. Given the sibling 'create_booking' tool, the description should explicitly state this is for preliminary pricing only and does not reserve inventory, or direct users to use this before creating a booking.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.