Rezdy Agent MCP Server

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

No annotations provided, so description carries full burden. While 'Search' implies read-only, the description fails to disclose pagination behavior, rate limits, whether sessions are real-time, or what the return structure contains. Only behavioral hint is 'with pricing', indicating price calculation occurs.

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?

Single sentence efficiently conveys core purpose without redundancy. Front-loaded with action verb and no filler text.

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?

Adequate for a 6-parameter search tool with complete schema coverage, but gaps exist due to missing output schema and zero annotations. Description should ideally explain return values or response structure given no output_schema exists.

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 parameters are fully documented in structured fields. The description adds minimal semantic value beyond the schema, only hinting at the 'quantities' parameter purpose via 'with pricing'. Baseline score appropriate for high-coverage schema.

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 specific verb 'Search' with clear resource 'availability sessions' and scope 'for a product with pricing'. It distinguishes from sibling 'search_products' by focusing on availability sessions rather than product catalogs, though it could further clarify what constitutes an availability session.

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?

Description provides no guidance on when to use this tool versus alternatives like 'get_product' or 'quote_booking'. No mention of prerequisites (e.g., obtaining productId first) or when not to use it.

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