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 full burden. It mentions 'confirmed' status but fails to disclose critical behavioral traits: payment processing implications (despite the paymentType enum), whether the operation is idempotent, error handling for unavailable inventory, or if notifications are sent. For an 11-parameter mutation operation, this is insufficient.

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 extremely concise (3 words) and front-loaded with the operative verb. While no words are wasted, the brevity is inappropriate for the tool's complexity (11 parameters with nested objects), resulting in under-specification rather than efficient communication.

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 the tool's complexity (nested customer/participant objects, payment processing, 11 parameters), the absence of an output schema, and lack of annotations, the description provides inadequate context. It omits return value expectations, error scenarios, and business logic critical for a booking creation mutation.

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 description coverage is 100%, establishing a baseline of 3. The description adds no supplementary context about parameter semantics, validation rules, or relationships between nested objects (e.g., how quantities relate to productId), but meets the minimum given the schema's completeness.

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 states the basic verb and resource ('Create a confirmed booking'), but is nearly tautological with the tool name 'rezdy_agent_create_booking'. It adds minimal value with the word 'confirmed' but fails to distinguish from siblings like 'rezdy_agent_quote_booking' (which likely creates provisional quotes vs confirmed bookings) or clarify the scope of 'confirmed'.

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?

No explicit guidance on when to use versus alternatives (e.g., when to use quote_booking instead), prerequisites, or preconditions. The word 'confirmed' provides only implicit contrast to the sibling quote tool but offers no actionable decision criteria.

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