Zoom 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 effectively describes key traits: it's a debug tool that simulates resolution without actual fetching, shows matching aliases and found locations, and indicates API call implications. However, it doesn't specify error handling, rate limits, or authentication needs, leaving some behavioral aspects uncovered.

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 well-structured and front-loaded, starting with the core purpose. Each sentence adds value: the first states the tool's function, the second explains its utility, and the third gives concrete use cases. There is no redundant or wasted text, making it highly efficient.

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 moderate complexity (debugging/resolution without annotations or output schema), the description is mostly complete. It covers purpose, usage, and parameter intent effectively. However, it lacks details on return format (e.g., structure of resolved data) and error scenarios, which would enhance completeness for a debug tool.

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 0% description coverage, so the description must compensate. It adds meaningful context for the 'location_query' parameter through examples like 'DEN1' and 'Floor 1', clarifying it's a string for testing location matching. While it doesn't detail syntax constraints, it provides sufficient semantic understanding beyond the bare 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 clearly states the tool's purpose: 'Test how location queries get resolved without fetching rooms.' It specifies the verb ('Test') and resource ('location queries'), and distinguishes it from sibling tools by emphasizing it's for debugging/resolution rather than actual data fetching. The examples ('How would "DEN1" be resolved?') reinforce this specific scope.

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 explicit guidance on when to use this tool: 'USE THIS to understand what locations will be searched before running expensive room queries.' It contrasts with siblings by positioning it as a preparatory/debugging step to avoid costly operations, and includes perfect-use-case examples that clarify its role versus tools like get_room_details or get_zoom_rooms.

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