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 but provides almost none. It does not confirm this is a read-only operation, describe the return format (list of products), explain pagination behavior (despite limit/offset parameters), or mention any rate limiting or performance characteristics.

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 single sentence is efficiently constructed and front-loaded with the action verb. While extremely brief, it contains no redundant words. However, given the high complexity (13 parameters, no output schema), it arguably errs on the side of under-specification rather than optimal conciseness.

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 tool with 13 parameters and no output schema or annotations, the description is inadequate. It fails to describe what data structure is returned, does not clarify that this queries a catalog rather than availability/bookings, and omits pagination guidance despite having pagination parameters.

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%, so the schema adequately documents all 13 parameters. The description adds only the context 'from all suppliers' which subtly hints at the supplierId filter purpose, but provides no guidance on parameter interactions, query logic (AND vs OR), or recommended pagination defaults.

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 provides a clear verb ('Search') and resource ('marketplace products'), and the phrase 'from all suppliers' establishes scope. However, it does not explicitly distinguish from the sibling 'rezdy_agent_get_product' (single retrieval by ID vs. search/filtering) or clarify when to use this versus 'rezdy_agent_search_availability'.

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?

There is no explicit guidance on when to use this tool versus alternatives like 'get_product' or 'search_availability'. It does not mention that all parameters are optional (0 required) or suggest typical query patterns for the 13 available filters.

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