Rezdy Agent MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a write operation via 'Create' but fails to disclose idempotency, uniqueness constraints (e.g., email duplicates), return values, or error handling behavior.

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 at four words with zero redundancy. It is front-loaded with the essential verb and resource, though its brevity arguably under-serves the tool's complexity (8 parameters, nested objects).

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 presence of 8 parameters (including a nested address object), 3 required fields, and no output schema or annotations, the description is insufficiently complete. It omits return value structure, side effects, and the significance of required versus optional fields.

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 has 100% description coverage, documenting all 8 parameters including nested address fields. The description adds no parameter-specific context, meeting the baseline score for high-coverage schemas where the structured data already suffices.

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 core action ('Create') and resource ('customer profile'), providing a grammatical sentence that expands slightly on the tool name. While it lacks the field-level detail of the 'update_drive' example, it unambiguously identifies the tool's function.

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 provides no guidance on when to use this tool versus siblings like 'rezdy_agent_search_customers' or 'rezdy_agent_get_customer'. It does not mention prerequisites (e.g., checking for existing customers) or exclusion criteria.

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