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 'Get' implies read-only, the description fails to disclose what 'detailed information' includes, error handling for invalid IDs, rate limits, or authentication requirements.

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, front-loaded with verb, no redundancy. However, given zero annotations and no output schema, the extreme brevity leaves critical behavioral context undocumented.

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 single-parameter getter with complete schema coverage, the description meets minimum viability. However, lacking annotations and output schema, it should explicitly state this is a safe read operation and clarify the relationship to search tools.

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 coverage is 100% with 'productId' fully documented. The description adds domain context ('marketplace product') aligning with the parameter, but does not add syntax details, ID format requirements, or examples beyond what the schema provides.

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 'Get' and resource 'marketplace product'. The word 'specific' effectively distinguishes this from sibling 'search_products', clarifying this retrieves one item by ID rather than filtering many.

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 guidance provided on when to use this versus the sibling 'search_products' tool. Missing explicit instruction that this requires an exact product ID while search_products is for discovery/filtering.

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